Do you need GitHub access?
Not everyone on GOV.UK requires GitHub access, as much of what we do is in the open. However, if your role requires it, you can be added to the alphagov org.
If you’re a content designer, your request should go through Zendesk (see example ticket).
If you’re an engineer or contractor, ask a developer on your team who has production access (such as your tech lead) to follow the steps below. If no developers on your team are available, ask in the Technical 2nd Line Slack channel for someone to add you.
Granting GitHub access
These steps should only be completed by a developer with production access:
- Add the person to the relevant file in govuk-user-reviewer.
- Email email@example.com, asking for the person to be added to the org. You should include:
- A link to the pull request created in the previous step.
- The GitHub username to be added.
- The name of the team they should be added to (see Teams in alphagov). This is usually “GOV.UK” for engineers and contractors, and “GOV.UK Content Designers” for content designers.
- An explanation of which team the person is working in, and in what role.
- An alphagov admin will process the request. The person will receive an invite from GitHub in their inbox, which they will have to accept.
Teams in alphagov
There are several core ‘teams’ set up in GitHub, under the alphagov org.
GOV.UK Content Designers. This team allows the user to create a branch in a GOV.UK repository and open a pull request, but only a developer can merge the request. Only content designers should be added to this team.
GOV.UK. This team gives write access to private repos (see Configure a GitHub repo), as well as integration admin access to the CI environment.
GOV.UK Production Deploy. Grants deploy access to staging and production.
GOV.UK Production Admin. Grants admin access to staging and production.