I'm an artist. For years, I have had the habit of always Pulling before I Commit/Push. Till recently, I would Pull and if there was an incoming merge conflict, the Merge Conflict popup would show up and then I would have an opportunity to right-click the conflicted file and resolve it. Again, all without Committing first.
Now it seems like Sourcetree has changed and it expects me to Commit BEFORE Pulling. Says so in the popup.
WHY has this changed? And is there a way to put it back how it was? I would rather have an opportunity to Reset my file before Committing it, if I don't want to Resolve. And for an artist, un-committing requires a command line.
Hello! Which OS are you using?
We enforce this behavior because the docs actually warn about this topic:
Warning: Running git merge with non-trivial uncommitted changes is discouraged: while possible, it may leave you in a state that is hard to back out of in the case of a conflict.
Due to this, I'd advise that you actually do the following:
For un-committing: you can right-click the commit in the History view and select "Reverse commit".
Supported Platforms macOS Windows We recently introduced support for additional hosting services such as GitHub Enterprise, GitLab (Cloud, Community Edition, Enterprise Edition), and...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events