Repository access via GitHub Teams

[NickWalt01]

Hello All

As part of our ongoing work to improve access to our GitHub repositories via team access rather than direct user access we would like your feedback on the new automation we intend to implement soon.

Why are we making these changes: Better alignment with organisational best practices, improve repository access management; ideally all users should have access to a repository via a managed team (excluding outside collaborators), team maintainers can then self manage user access to a team and repository, and it will aid future automation that focuses on teams.

This automation will apply to users who have direct access to a repository and no team access.

The Operations-Engineering team will automate moving users into teams with the same repository access. This involves creating new team/s for the repository based on the direct user access and automatically moving the user into that team. Example: A user with write access to the the operations-engineering repository would be moved to a new team called operations_engineering_write_access_team. In future runs where a user is found to have direct access to the repository and a team has already been created for that repository with matching permissions the user will be automatically moved into that team. These teams will not be managed or monitored by the operations-engineering team.

This applies to MoJ organisation members and not outside collaborators.

We have an existing automated script that automatically removes a users direct access where that user has both direct access to the repository and access to the repository via a team. This will continue as-is.

If you have any questions or concerns please contact #ask-operations-engineering