I'm working on a big project using Mercurial. I had local changes to a few files, and a colleague committed changes to one of those files to our central repository. Before committing my changes to my local repository, I decided to do a pull and an update. Now, Sourcetree is listing the simultaneously modified file twice in the pending changes view.
Is this normal or a bug? If it's normal, how should I do my commit now?
This is a bug, but I can't see how it could happen, I can't reproduce it here. The way you query general file status and merge status is separate in hg, so we query both then merge the results based on the path, but in your screenshot the paths clearly match 100%.
You can still go ahead and commit - just allow all the file entries to be checked in the commit dialog (this is required for merges anyway, you have to commit everything) and it will still work fine. I'll try to figure out how this edge case might have occurred.
Supported Platforms macOS Sourcetree has a lot to offer and, like many developer tools, finding and using it all can be a challenge, especially for a new user. Everyone might not love ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot