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

Author: Dag Calafell

Share This Post On
Share via
Copy link
Powered by Social Snap