Confusing and inconsistent state management in working copies

6/10 Medium

The combination of working copy files and local Git repository state creates a 'magical state' where certain operations become impossible (e.g., changing branches after a broken merge). Developers must search for solutions rather than having straightforward recovery paths like SVN's simple delete and update.

Git
Category
dx
Workaround
none
Stage
debug
Freshness
persistent
Scope
single_lib
Upstream
wontfix
Recurring
Yes
Buyer Type
individual

Sources

Collection History

Query: “What are the most common pain points with Git for developers in 2025?”4/5/2026

The combination of files in your working copy and local Git repository creates some kind of magical 'state' defining what kind of operations you are allowed to do. And it is easy to get your working copy to a 'state' where you can't do the things you want, for example change the branch.

Created: 4/5/2026Updated: 4/5/2026