/
Setting Up Branch Policies

Setting Up Branch Policies

The following branch policies should be applied to the dev and main branches for all projects.

The release branches brought over from the TFS migration should be locked as no further changes should be made to them.

For the dev branch, limit merge types to Squash merge to ensure the branch is clean.

For the main branch, limit merge types to Rebase and fast-forward.

Team Skyblazers or Team Avro Arrows should be set as an automatically included reviewer.

Updating Branch Policies for the Removal of an Existing Team

Go to the list of repositories:

Settings · Repositories (DSD-CIVAV Support) - Settings (azure.com)

For each repository, do the following:

Click Policies

For each branch that has the badge icon, click the branch to configure it:

Delete the reviewer you no longer want:

If multiple “Team Avro Arrows” or any permissions appear multiple times, it is safe to delete the one that was not inherited (“Inheritance” appears on the right under the Inheritance column).

Related content

Machine Code Generator - Entrust Guard Identity
Machine Code Generator - Entrust Guard Identity
Read with this
How-to use Git with Visual Studio
How-to use Git with Visual Studio
More like this
Azure
Read with this
Migrate project repo from TFS to DevOps
Migrate project repo from TFS to DevOps
More like this
Civil Aviation IT Portfolio
Civil Aviation IT Portfolio
Read with this
How to set up working environment and make code changes for ROFS
How to set up working environment and make code changes for ROFS
More like this