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?
AS007
Highly Voted 4 years, 5 months agoYusho
Highly Voted 4 years, 2 months agoozbonny
Most Recent 8 months, 1 week agovsvaid
10 months, 1 week agoyana_b
1 year, 2 months agoxRiot007
1 year, 3 months agosyu31svc
2 years, 2 months agoUnknowMan
2 years, 5 months agoshash_ank
2 years, 4 months agordemontis
2 years, 7 months agolugospod
2 years, 8 months agoSurda
2 years, 9 months agoDrewL
3 years, 2 months agoFred64
4 years, 5 months ago