Skip to main content

Github

For personal GitHub access, SSO licence retention and account troubleshooting, use GitHub onboarding.

GitHub teams

Create two GitHub teams for your team:

  1. Click on the ‘teams’ tab.
  2. Create a team called <team-name>.
  3. Link this team to your Microsoft Entra ID group created as part of Microsoft Entra ID onboarding. This means team members are automatically added when they join.
  4. Create a team called <team-name>-admins.

GitHub teams should be linked to a team Microsoft Entra ID group where possible.

If a team is not linked to Microsoft Entra ID, a senior member of the team must manage membership.

Repository access

Repository access must be managed through GitHub teams:

  • All repositories should be administered by the team who owns them.
  • Access should be managed through GitHub teams, not individual users.
  • Do not add collaborators from outside the organisation.
  • If no one from your team has access, follow asking for help to request help from org admins.

Create a GitHub repository

Any developer added to the HMCTS GitHub organisation can create a new GitHub repository.

See creating a GitHub repository for naming, visibility, team access and branch protection guidance.

After the repository is created, follow Jenkins setup to make sure the repository can be scanned, built and deployed.

This page was last reviewed on 29 July 2026. It needs to be reviewed again on 29 January 2027 by the page owner platops-build-notices .
This page was set to be reviewed before 29 January 2027 by the page owner platops-build-notices. This might mean the content is out of date.