-
Notifications
You must be signed in to change notification settings - Fork 319
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 Repository Administrators #4128
Comments
Updating issue after ping interval. See its status below. The number of teams with admin permission on this repository is greater than the allowed maximum value. |
3 similar comments
Updating issue after ping interval. See its status below. The number of teams with admin permission on this repository is greater than the allowed maximum value. |
Updating issue after ping interval. See its status below. The number of teams with admin permission on this repository is greater than the allowed maximum value. |
Updating issue after ping interval. See its status below. The number of teams with admin permission on this repository is greater than the allowed maximum value. |
Overrode to allow the 3 necessary teams. This highlighted that all of TLC crew had admin access, which is too much — TLC should have standard write access or manage, at most. TLC leads have been added as a separate group and given admin permissions. |
Reopening issue. See its status below. The number of teams with admin permission on this repository is greater than the allowed maximum value. |
PR #4145 should close this. |
This issue was automatically created by Allstar.
Security Policy Violation
The number of teams with admin permission on this repository is greater than the allowed maximum value.
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: