3 ms·
An actually sane VCS would stash your changes when switching to another branch amd restore the stash when switching back, at least by default. Git instead hand
by gmueckl 6y ago
An actually sane VCS would stash your changes when switching to another branch amd restore the stash when switching back, at least by default. Git instead handles this in a way that introduces a handful of potentially data shredding gotchas.
- hctaw 6y agoI always just commit my changes and switch branches, come back and squash.
- bob1029 6y agoThis is my go-to as well. I use commit messages like "intermediate work" and then push to origin to make it clear things are in a temporary state from the outside (i.e. someone looking at exploding check builds). You can usually infer exactly what I am working on just by reading the latest commit messages on all of my branches.