BenchMark Quizzes by MDFT Pro

Select The Correct Commit Message Format

You work for MDFT Pro, a well-known training agency that develops educational software for its students. As a DevOps engineer, you manage a project named EDU_PROJ using Azure Boards for work item tracking, and Azure Repos for source code management.

Your team lead, Claire, reported a critical bug in the student registration module that’s preventing new users from enrolling in courses. This bug was documented as work item #123 in Azure Boards. You’ve identified and fixed the issue in your code.

Now, when you commit your changes to the repository, you need to ensure that the work item is automatically updated to a “Resolved” state. What should you add to your commit message to properly link and resolve this work item?

Choose the correct answer from the options below.

Explanations for each answer:

Fixes AB#123 is correct. This is the correct format for Azure DevOps commit messages to link work items. The 'Fixes' keyword will not only link the commit to the work item but also automatically resolve the work item when the commit is pushed, setting its state to 'Resolved'.
AB#123 Fixed is incorrect. This format doesn't follow Azure DevOps' commit message conventions. The keyword 'fixed' should precede the work item number, not follow it.
AB#123 is incorrect. This format is incomplete. Simply referencing the work item ID without a proper keyword (like 'Fixed' or 'Resolved') will link the commit to the work item but won't automatically change its state to 'Resolved' as required by the question.
Resolved #AB123 is incorrect. While 'Resolved' is a valid keyword (it maps to the work item state 'Resolved'), the format for referencing the work item is incorrect. For Azure Boards integrated with Azure Repos, you should use the syntax 'AB#123'.

Learn more about linking work items in commit messages:

Linking Work Items

Exam Preparation Quiz

Select The Correct Commit Message Format