Microsoft · AZ-401 · BETA
Branching strategies and pull request workflows
AZ-401 · Lesson 4 of 18 · 24:23
YouTube loads only after you press play. This chapter opens at its timestamp in the full course. Watch on YouTube ↗
In this lesson
Lesson 4 of the free AZ-401 series (domain 2): trunk-based development, feature branches, GitHub flow, release branches, Git flow, Git worktree for parallel work, Azure Repos branch policies and merge types, GitHub rulesets, and the protections that apply to Copilot cloud agent. With three quick checks and a recap.
Preview the topics
- A developer is halfway through a feature when an urgent fix is needed on the release branch, and the feature changes are not ready to commit. What lets the developer fix the release branch in parallel?
- Contoso wants every pull request into main on Azure Repos to land as one single commit, to keep the history clean. Which policy setting fits?
- A Contoso developer asks Copilot cloud agent to fix a bug, and wants to approve its pull request personally, to merge it faster. What happens?