L1. Flow of Work and Traceability: GitHub Flow, Azure Boards & Work Item Integration

What Is GitHub Flow?

GitHub Flow is a lightweight branching model that keeps the main branch always deployable. Unlike Git Flow, which maintains multiple long-lived branches (develop, release, hotfix), GitHub Flow uses only main and short-lived feature branches.

The workflow is straightforward: create a feature branch off main, commit changes, open a pull request for review, merge after approval, and delete the branch. Every change requires a pull request before merging to main. This ensures code review happens before production code changes and main is never broken.

Why Traceability Matters

Traceability answers the question: "Why did this code change, and what work item justified it?" For audits and compliance, you need a complete chain from requirement to code to release.

A full traceability chain looks like this:

• User story or bug work item
• Feature branch created for that work item
• Commits referencing the work item ID
• Pull request linking the work item
• Build and test pipeline run
• Release containing that code

Without traceability, auditors cannot verify that changes follow proper change control processes.

Linking Work Items in Azure Boards

Azure Boards integrates with GitHub through the AB# syntax. When you include AB#123 in a commit message or PR description, Azure Boards automatically links that change to work item 123:

git commit -m "Fix authentication flow AB#456"

The commit now appears on work item 456's timeline. Teams can also create branches directly from a work item in Azure Boards, and the branch name is pre-populated with the work item ID for easy reference.

GitHub Issues and Closing Keywords

When using GitHub Issues instead of Azure Boards, use closing keywords in PR descriptions to auto-close issues:

This ensures issues are closed automatically and linked to the PR that resolved them, keeping GitHub's issue tracker synchronized with your code.

The Azure Boards GitHub Connector

The Azure Boards GitHub Connector bridges the gap between a GitHub repository and an Azure DevOps project. Once configured, every commit and pull request on GitHub automatically appears on the corresponding Azure Boards work item's timeline without any manual linking.

This allows teams to use GitHub for code while maintaining sprint planning and work tracking in Azure Boards. The connector handles the linking automatically, reducing manual overhead and keeping both systems in sync.

Feedback and Notifications

GitHub Flow supports asynchronous collaboration through notifications. Team members receive alerts when:

• A pull request is opened requesting their review
• Comments are added to an issue or PR
• Their review is requested or dismissed

These notifications keep stakeholders informed without requiring them to switch between tools constantly. Exam tip: The AZ-400 exam tests traceability chains and the relationship between GitHub Flow, Azure Boards, and compliance. Remember: GitHub Flow makes main always deployable through short-lived branches and PR reviews, while AB# syntax and the Connector enable full work item tracking.