Nice explanation. I preferred the merge conflict detection in Visual Studio. Where you saw 3 columns; Left Source, Right Source & Final. Giving you check boxes on each conflict line to decide what the Final will look like. If you checked both you got an extra line. Especially handy for variable declarations, comments & formatting changes.
Great video. If there are multiple conflicts, I assume it will let you resolve them one by one? What has me concerned is when it said take whole file. I wasn’t sure if that pertained to the single conflict or all conflicts.
Good Question, this would require manual intervention in merging those changes together / looking into the cherry picking option, I will cover this scenario in a separate video :)
Nice explanation. I preferred the merge conflict detection in Visual Studio. Where you saw 3 columns; Left Source, Right Source & Final. Giving you check boxes on each conflict line to decide what the Final will look like. If you checked both you got an extra line. Especially handy for variable declarations, comments & formatting changes.
Very detailed explaination, thanks a lot!!!
Excellent demo! Thanks
Great explanation, looking forward to see cherry picking scenarios in Azure DevOps
This is great! Thank you!🙏🏻
Great video. If there are multiple conflicts, I assume it will let you resolve them one by one? What has me concerned is when it said take whole file. I wasn’t sure if that pertained to the single conflict or all conflicts.
Very useful, thanks!
What if we want to take both? Changes in the same file..
Good Question, this would require manual intervention in merging those changes together / looking into the cherry picking option, I will cover this scenario in a separate video :)
@@mr.ktalkstech sure thank you sir..please create a video on it.. that helps many folks.🙌🙌
This question was asked in my recent interview but i'm unable to answer