You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
breakdown of who should be granted access to the three tiers of permissions for our repo:
Details by team
311-data (read access):
All users (should include ex-311 data members, if removed from write/maintainers, make sure to add them here)
311-data-write:
All active 311 participants marked active as per roster (may need to update who is active/inactive on roster as well)
311-data-maintainers:
(this is different from being a maintainer on another GitHub team e.g., write-maintainer, read-maintainer, which enables you to add and remove people from the team) Confirm with @ExperimentsInHonesty (Bonnie) to determine who should still be here no one, we don't use this team, but we are leaving it for now
311-data-admin:
One PM (so that they can edit issue templates), possibly the tech lead if they need it for something specific like setting up branch protections. Permission should be removed when they no longer need it.
The text was updated successfully, but these errors were encountered:
edwinjue
changed the title
Review and update github access for general/write/maintainers
Review and update github access for read/write/maintainers
Mar 30, 2023
Overview
We need to clean up the GitHub team permissions on this project, so that everyone has the appropriate level of access.
Action Items
Resources/Instructions
Teams
Permission Rules
breakdown of who should be granted access to the three tiers of permissions for our repo:
Details by team
311-data (read access):
All users (should include ex-311 data members, if removed from write/maintainers, make sure to add them here)
311-data-write:
All active 311 participants marked active as per roster (may need to update who is active/inactive on roster as well)
311-data-maintainers:
(this is different from being a maintainer on another GitHub team e.g., write-maintainer, read-maintainer, which enables you to add and remove people from the team)
Confirm with @ExperimentsInHonesty (Bonnie) to determine who should still be hereno one, we don't use this team, but we are leaving it for now311-data-admin:
One PM (so that they can edit issue templates), possibly the tech lead if they need it for something specific like setting up branch protections. Permission should be removed when they no longer need it.
The text was updated successfully, but these errors were encountered: