One-Off Backfill Tool for Managing GitHub Permissions as Code #4091
+13,432
−5,816
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
|
Could you do this in stages instead of all 2000+ files at once? i.e. could just do the special teams first? and a few plugins? |
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.
Description
This pull request introduces a one-off backfill tool that transfers GitHub permissions into a YAML file. This tool is designed to prepare for #3998, which focuses on managing GitHub teams' permissions as code. To ensure the data remains current, I will update this backfill tool just before both this PR and #3998 are ready to merge.
Discussion Points:
Auto-generation of YAML Files for Missing GitHub Teams:
During the backfill process, I have identified approximately 500 teams currently only on GitHub (You can view the detailed list here). Should I auto-generate YAML files for all these teams to avoid discrepancies and prevent overwriting GitHub team settings when #3998 goes live?
Auto-generation of YAML Files for Missing GitHub
SpecialTeams:Currently, our
teams/directory contains YAML files for only 5 out of about 50 special teams(A special team is a team injenkinscithat has more than 1 repo permission) identified on GitHub. Should I create YAML files for the remaining teams to ensure we can manage other permissions in YAML format in the future?Please share any thoughts or suggestions you have. I really appreciate your time and help.