-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Security Policy violation Branch Protection #99
Comments
Updating issue after ping interval. See its status below. No protection found for branch main |
The policy result has been updated. Dismiss stale reviews not configured for branch main |
The policy result has been updated. No protection found for branch main |
Updating issue after ping interval. See its status below. No protection found for branch main |
8 similar comments
Updating issue after ping interval. See its status below. No protection found for branch main |
Updating issue after ping interval. See its status below. No protection found for branch main |
Updating issue after ping interval. See its status below. No protection found for branch main |
Updating issue after ping interval. See its status below. No protection found for branch main |
Updating issue after ping interval. See its status below. No protection found for branch main |
Updating issue after ping interval. See its status below. No protection found for branch main |
Updating issue after ping interval. See its status below. No protection found for branch main |
Updating issue after ping interval. See its status below. No protection found for branch main |
This issue was automatically created by Allstar.
Security Policy Violation
No protection found for branch main
Issue created by GSA-TTS Allstar. See remediation hints in the README.
This issue will auto resolve when the policy is in compliance.
Issue created by Allstar. See https://github.com/ossf/allstar/ for more information. For questions specific to the repository, please contact the owner or maintainer.
The text was updated successfully, but these errors were encountered: