# Install git-spice with Homebrew

Manage stacked Git branches. Version 0.31.2 via Homebrew; verified 2026-07-27.

## Install

```sh
sudo av install brew:git-spice
```

Additional install commands:

### macOS

- Homebrew (100%):

```sh
brew install git-spice
```

  Evidence: provider-native install command

## Package facts

- **Package key:** brew:git-spice
- **Package manager:** Homebrew
- **Version:** 0.31.2
- **Source summary:** Manage stacked Git branches
- **Homepage:** <https://abhinav.github.io/git-spice/>
- **Repository:** <https://github.com/abhinav/git-spice>
- **Last updated:** 2026-07-27T14:57:49+02:00
- **Generated:** 2026-08-03T00:40:33+00:00

## Executables

- git-spice (alias)

## Install behavior

- Bottle: not available

## Freshness

- Page generated: 2026-08-03
- Package-manager version: 0.31.2
## Project history and usage

git-spice is a Git stacking tool that manages dependent branches and submits them as pull requests or merge requests across several forge providers.

### Project history

The project repository was created in 2023, with early public code and alpha tags appearing in 2024. Its documentation defines stacking as creating branches or change requests that build on top of each other so related work can stay small and reviewable while preserving dependency order.

git-spice grew from local branch navigation and restacking into a forge-aware workflow tool. The README and documentation describe support for GitHub, GitLab, Bitbucket, Gitea, Forgejo, and Codeberg-style workflows, while the changelog records later additions such as fork-based contribution flows, Ubuntu PPA packaging, and experimental stack merge commands.

### Adoption history

Adoption belongs to the stacked-PR niche, a workflow popular among engineers who split large changes into reviewable layers. The project documents incremental adoption, offline-first local state, shorthand commands, and a visible user-community section, making it part of the newer wave of Git tools that bring Phabricator-style stacked change review to GitHub and GitLab users.

### How it is used

Practitioners use git-spice through the git-spice executable or the gs shorthand. Typical flows create or track stacked branches, submit one branch or an entire stack, sync with trunk, delete merged branches, restack dependent branches after base changes, and keep local metadata in Git configuration.

### Why package nerds care

git-spice matters to package and developer-tool watchers because it is a forge-neutral, open-source entry in the stacked-branch space. Its packaging in Homebrew and Nix makes a workflow that once depended on hosted services or workplace-specific tooling easier to install as a normal CLI.

### Timeline

- 2023: GitHub repository was created.
- 2024: First public code and alpha tags appeared.
- 2026: Changelog entries documented fork workflows, additional forge support, and stack merge experiments.

### Related projects

- The related practice area is stacked pull requests and merge requests, with git-spice positioning itself as a Git-compatible branch manager rather than a replacement for Git.

### Sources

- <https://abhinav.github.io/git-spice>
- <https://formulae.brew.sh/formula/git-spice>
- <https://github.com/abhinav/git-spice>
- <https://github.com/abhinav/git-spice/blob/main/CHANGELOG.md>
- <https://github.com/abhinav/git-spice/blob/main/README.md>


## Security Notes

narrow executable package without higher-risk signals.

- **Geiger risk:** green / low
- narrow executable package without higher-risk signals


## Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.


## Configuration files

- Unix: .git/config, ~/.gitconfig, ~/.config/git/config, /etc/gitconfig

## Combined YAML source

View the package source record on GitHub. [combined/git-spice.yml](https://github.com/automic-vault/db/blob/main/combined/git-spice.yml)


## Sources

- Nucleus package database
- Geiger risk classifier
- curated configuration and credential file locations
- curated package history
- pkgdb category and tag curation