You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
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".