2 ms·
Git should really steal the only thing I like about perforce, many uncommited change lists. It should be an easy workflow change to add 'named stages' along si
by jayd16 3y ago
Git should really steal the only thing I like about perforce, many uncommited change lists. It should be an easy workflow change to add 'named stages' along side the default stage. That way you can just leave changes in a different stage, tracked but uncommitted.
- postmodest 3y agoIs that different to git stash?
- jayd16 3y agoYeah, they stay in the working set but files are marked for different commits. Ideally git could do it at the line level instead of by file.
- dingnuts 3y agoUnless I have misunderstood your feature request, that feature exists, and it's called "worktrees" Worktrees allow you to have multiple branches open potentially with dirty state on any or all of them https://git-scm.com/docs/git-worktree https://git-scm.com/docs/git-worktree
- jayd16 3y agoNo I don't think that is a similar feature. It looks like worktrees are put on different paths and by default do not operate on the same commit. My feature request is about having n stages instead of one so uncommitted work can be organized better while staying in the usual working copy. How would I accomplish this with worktrees?