Question 321 · 540 in bank
Your company uses a Git repository in Azure Repos to manage the source code of a web application. The master branch is protected from direct updates. Developers work on new features in the topic branches. Because of the high volume of requested features, it is difficult to follow the history of the changes to the master branch. You need to enforce a pull request merge strategy. The strategy must meet the following requirements: ✑ Consolidate commit histories. ✑ Merge the changes into a single commit. Which merge strategy should you use in the branch policy?
Show answer
Answer: A
Explanation
Squash merging is a merge option that allows you to condense the Git history of topic branches when you complete a pull request From https://docs.microsoft.com/en-us/azure/devops/repos/git/merging-with-squash?view=azure-devops A is the answer
Source: Adapted from community discussion — syu31svc


