Remove legacy bors permissions #1586
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
MarcoIeni
previously approved these changes
Oct 22, 2024
This PR removes bors review/try permissions for repositories that are no longer managed by bors.
Kobzol
force-pushed
the
bors-permissions-cleanup
branch
from
8bba7a3 to
85a761d
Compare
rylev
approved these changes
Oct 23, 2024
|
These people were actually causing CI to fail, because they were not in any teams or repos. They were only being accepted by CI, because they still had the legacy bors permissions. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR removes bors review/try permissions for repositories that are no longer managed by bors.