3 ms·
I successfully use [stgit][1] (for 10 years) for private commits and pretty much for the rest of near-git workflows. [1]: https://stacked-git.github.io/ https:
by bvrmn 4y ago
I successfully use [stgit][1] (for 10 years) for private commits and pretty much for the rest of near-git workflows.
[1]: https://stacked-git.github.io/ https://stacked-git.github.io/
- AvImd 4y agoDoes stgit help with the following scenario: 1. I want some changes in my repo to be persistent whenever I switch to a new branch, pull, or merge a remote. 2. They should not be shown in git status. 3. They should not be pushed. From skimming the front page I haven't found whether something like this is supported. I see that with stgit I can `stg pop` my "persistent changes" before pushing to the remote and then apply it again with `stg push` but that requires that I use stg commands to create patches instead of `git commit`.
- bvrmn 4y agoFor this case `git stash` is enough.