Set policies like: ○ Require a minimum number of reviewers. ○ Build validation (run a pipeline before merging). ○ Limit who can push directly. ○ Require linked work items. Example: For main, you might set: ● 2 code reviewers minimum. ● Build must pass. ● No direct pushes (only PR merges). 4⃣ How do you enforce code reviews or pull request policies?

You enforce them with branch policies.

Azure DevOps lets you require:

• A minimum number of reviewers (e.g., 2).
• Approval from code owners.
• Successful builds before merge.

Follow:

• Linked work items or comments resolved.

Example:

When a developer submits a pull request to merge feature/login, the PR won’t

complete until:

• At least two reviewers approve it.
• The build pipeline passes.
• All comments are marked resolved.

This ensures code quality and consistency.

5⃣ How do you resolve merge conflicts in Azure Repos?

Merge conflicts happen when two people change the same part of a file.

How to resolve:

Pull the latest changes:

git fetch origin

git merge origin/main