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 using Visual Studio 2017 v13.3.0 (source control is disabled) and SourceTree v2.7.3. Twice now, I've made changes, committed them, pushed them -- and then lost the changes in the process. NOTE: A fetch does not fix this after it happens. Nor does it happen all the time, only twice so far since the SourceTree update to 2.7.3.
The behavior is this:
I'm not sure which is doing what here but I would expect SourceTree to recognize there have been changes if Visual Studio reloads the solution and everything is back to what it was.
NOTE: Since someone may ask, "Why use SourceTree when you have source control in Visual Studio?", it is because I work in many different tools and languages, even within the same project, and want to use a single tool to manage my source control.