Skip to content

Azure DevOps - Branch Policies & Security

week_twentythree - Azure DevOps Repos


duration: 1 week


ForgTech company wanna test your ability to deliver their requirements into their Azure DevOps projects. This will help you build a good reputation. The purpose of this task is to protect their main branch from unattended changes, as well as configure branch users permissions The FrogTech Tech Lead Team requests to protect the main branch based on the following requirements:

  1. Protect merging on the Main branch, and only accept merges over pull requests.
  2. Deny pusher to approve his changes.
  3. Force tech lead to review for all changes.
  4. Protect merging on the main branch from non-standard branch names, the standard branch names should follow below name conventoin.
# -------------------------------------------------------
# Allowed patterns:
# 1. feat|fix|chore|refactor|docs|test/<workItemID>-description_context
# - Work item = 5–7 digits
# - Description = lowercase letters, numbers, dot, underscore, hyphen
# Example: feat/332200-add_new_pipeline
#
# 2. release/x.y.z
# -------------------------------------------------------
  1. Assign the DevOps team sufficient access to clone, edit, and push with new branches that follow the standards naming convention above

References: