AZ-400 ยท Flow of work and traceability
Flow of work and feedback cycles
GitHub Flow vs work-item driven flow, WIP and small batches, notifications and subscriptions, GitHub Issues as a feedback channel, issue templates and labels.
Key points
- GitHub Flow: branch, commit, open a pull request, review, merge, delete the branch.
- A work-item driven flow starts from a tracked item (for example in Azure Boards) and links branches and PRs to it.
- Small batches and limited work in progress (WIP) bring feedback early.
- Issues, labels and templates structure feedback; notifications decide who hears about changes.
Source: https://docs.github.com/en/get-started/using-github/github-flow
Practice questions
In which repository folder do GitHub issue templates and issue forms live?
- .github/workflows
- .github/ISSUE_TEMPLATE
- docs/issues
- The repository wiki
Show answer
Answer: B. .github/ISSUE_TEMPLATE
Templates and forms are stored in .github/ISSUE_TEMPLATE. The docs folder or the wiki are not read by the issue chooser.
Which activities are part of GitHub Flow?
- Create a short-lived branch for the change
- Open a pull request to request feedback
- Maintain a permanent develop branch that mirrors production
- Merge the pull request after it is approved
- Freeze the default branch for the whole sprint
Show answer
Answer: A. Create a short-lived branch for the change, B. Open a pull request to request feedback, D. Merge the pull request after it is approved
GitHub Flow is branch, commit, pull request, review, merge. It does not use a permanent develop branch or a freeze of the default branch.
Limiting work in progress means starting more items in parallel so nobody is idle.
Show answer
Answer: False
False. WIP limits reduce parallel work so items finish sooner and feedback arrives earlier; too much parallel work raises cycle time.
Practice 8 questions on this topic in Bitzu
Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.
