Repository settings
Table Of contents
General settings
In the ‘Code’ tab:
- Edit repository details:
- Disable Releases and Packages
- Add Description and Website if needed
In the ‘Settings’ tab:
- Default branch name must be
main - Wikis
- Automatically delete head branches
Default branch policy
Create a new ruleset calles “Default branch policy”. It must be active and have Default branch as targeted.
For big repositories that require reviews
Examples: site backend, site frontend, other critical repositories.
- Restrict creations
- Restrict updates
- Restrict deletions
- Requite linear history
- Require deployments to succeed (IF YOU NEED THIS)
- Require signed commits
- Require a pull request before merging
- Required approvals: 1
- Dissmiss state pull request when new commits are pushed
- Require review from specific teams
- Require review from Code Owners
- Require approval of the most recent reviewable push
- Require conversation resolution before merging
- Require status checks to pass (THEN YOU HAVE CI/CD TESTS)
- Require branches to be up to date before merging
- Do not require status checks on creation
- Block force pushes
- Require code scanning results
- Require code quality results
- Automatically request Copilot code review
For small repositories that not require reviews
Examples: docs repositories.
For such repositories rulest is optional, but good to have.
- Restrict creations
- Restrict updates
- Restrict deletions
- Requite linear history
- Require deployments to succeed
- Require signed commits
- Require a pull request before merging
- Require status checks to pass
- Block force pushes
- Require code scanning results
- Require code quality results
- Automatically request Copilot code review
Post configuration setup
- Open ‘Projects’ tab and link repo to the project
- Add labels to the repository