Identify Merge Candidates Efficiently in Azure DevOps Version Control

Which branches have changes which need to be merged?

I am currently on a project with a large development team. Some of the developers are learning how to code X++, so one feature can turn into six check ins. Therefore, I needed a way to review all non-promoted changes before I rolled out the next release. I can check using Visual Studio with four clicks, but I have to check twenty or so…

Continue Reading Dag Calafell, III’s Article on their blog

Identify Merge Candidates Efficiently in Azure DevOps Version Control

Blog Syndicated with Dag Calafell, III’s Permission

More About This Author

Dag Calafell
Dag Calafell
Transformational Business Leader with ten years experience building effective state-of-the-art technology solutions to meet demanding manufacturing, customer, and user environments. Astute Negotiator who has saved hundreds of thousands of dollars in IT costs through strategic partnerships and technical innovation. Trusted Technology Expert who consistently delivers user-friendly technology solutions which surpasses business, customer requirements. Strategic Team Builder who mentors and transforms the IT organization to maximize business value at the lowest cost and risk.

Author: Dag Calafell

Transformational Business Leader with ten years experience building effective state-of-the-art technology solutions to meet demanding manufacturing, customer, and user environments. Astute Negotiator who has saved hundreds of thousands of dollars in IT costs through strategic partnerships and technical innovation. Trusted Technology Expert who consistently delivers user-friendly technology solutions which surpasses business, customer requirements. Strategic Team Builder who mentors and transforms the IT organization to maximize business value at the lowest cost and risk.

Share This Post On