| Crates.io | git-branch-stash-cli |
| lib.rs | git-branch-stash-cli |
| version | 0.11.2 |
| created_at | 2022-03-11 16:59:10.346336+00 |
| updated_at | 2025-08-05 18:07:09.639048+00 |
| description | Manage snapshots of your working directory |
| homepage | |
| repository | https://github.com/gitext-rs/git-branch-stash.git |
| max_upload_size | |
| id | 548356 |
| size | 69,297 |
Manage snapshots of your working directory
Dual-licensed under MIT or Apache 2.0
Backup and restore what your branches, including what they point at.
Download a pre-built binary (installable via gh-install).
Or use rust to install:
cargo install git-branch-stash-cli
See the uninstall method for your installer.
Once removed, git-branch-stash leaves behind:
.git/branch-stashRemoving this is safe and will have no effect.
git-branch-stashProtected branches: These are branches like main or v3 that git-branch-stash
must not modify. git-branch-stash will also rebase local protected branches against
their remote counter parts.
Run git-branch-stash --protected -v to test your config
git-branch-stash --protect <glob>.git-branch-stash as a team, you can move the protected branches from
$REPO/.git/config to $REPO/.gitconfig and commit it.Pull remote when working from a fork, where upstream is a different remote than
origin, run git config --add stack.pull-remote <REMOTE> to set your remote in $REPO/.git/config.
To see the config, run git-branch-stash --dump-config -.
Have an idea, we'd love to hear it!
There are probably git operations or workflows we haven't heard of and would
welcome the opportunity to learn more.