blog

Uncommitted changes messing up your sync in Git with Visual Studio

Published on
2 minute read

Sometimes when you try to Pull changes from the server to your local repository you get a “cannot pull because there are uncommitted changes”. This is uncommitted changes messing up your sync

I have been onsite in Athens working with a customer that is moving from StarTeam to Git. When you are moving from one source control system to another there are always difficulties and a difference in workflow between the systems. A workflow that works well in StarTeam might not in TFVC. However when you add that you are moving from a Server version Control System (SVCS) to a Distributed Version Control System (DVCS) you are going to go through a paradigm shift.

However, it can be the simplest of activities that bite you in the ass. For example, in most server based version control systems when you have made a bunch of changes locally and you want check-in to the server it is always prudent to do a “Get” first in order to verify that your local changes work with the latest version of the server. So you dutifully just do a “Get” and if your files locally conflict with the server you resolve the conflicts using the conflict resolution tools.

Uncommitted changes messing up your sync in Git with Visual Studio

When you try to do this in Git it complains that you have uncommitted changes that you either need to undo the changes and get rid of them, or you can commit them to the local repository.

In our server based scenario we have no choice but to do a merge from the server directly to our live edited files locally. If we complete the merge, and we messed up…. Well that’s just a little bit tough and you should have chosen better. So we have a lossey (or lousey) merge where we can potentially not end up with what we want and have no way back.

Git blocks this potential loss of code by forcing you to choose wither you want to lose the changes or persist them. Once they are persisted they can’t be lost without deliberately resetting the repository or deleting it. Although your workflow is changing it is for the better as you are less likely to have a frustrating issue.

DVCS is just better than SVCS…

tools-and-techniques blog dvcs git svcs visual-studio-2013 visual-studio

Connect with Martin Hinshelwood

If you've made it this far, it's worth connecting with our principal consultant and coach, Martin Hinshelwood, for a 30-minute 'ask me anything' call.

Our Happy Clients​

We partner with businesses across diverse industries, including finance, insurance, healthcare, pharmaceuticals, technology, engineering, transportation, hospitality, entertainment, legal, government, and military sectors.​

YearUp.org Logo
Slaughter and May Logo
Hubtel Ghana Logo
Philips Logo
ALS Life Sciences Logo
Akaditi Logo
Healthgrades Logo
Boxit Document Solutions Logo
Kongsberg Maritime Logo
Ericson Logo
Jack Links Logo
DFDS Logo
Xceptor - Process and Data Automation Logo
Alignment Healthcare Logo
Milliman Logo
Graham & Brown Logo
Cognizant Microsoft Business Group (MBG) Logo
Higher Education Statistics Agency Logo
New Hampshire Supreme Court Logo
Royal Air Force Logo
Department of Work and Pensions (UK) Logo
Nottingham County Council Logo
Ghana Police Service Logo
Washington Department of Transport Logo
Illumina Logo
MacDonald Humfrey (Automation) Ltd. Logo
Jack Links Logo
Microsoft Logo
Sage Logo
Lockheed Martin Logo