# Install git-tracker with Homebrew

Integrate Pivotal Tracker into your Git workflow. Version 2.0.0 via Homebrew; verified 2026-06-22.

## Install

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

Additional install commands:

### macOS

- Homebrew (100%):

```sh
brew install git-tracker
```

  Evidence: local Homebrew formula metadata

## Package facts

- **Package key:** brew:git-tracker
- **Package manager:** Homebrew
- **Version:** 2.0.0
- **Source summary:** Integrate Pivotal Tracker into your Git workflow
- **Homepage:** <https://github.com/stevenharman/git_tracker>
- **Repository:** <https://github.com/stevenharman/git_tracker>
- **Last updated:** 2026-06-22T14:03:32-07:00
- **Generated:** 2026-08-03T19:37:03+00:00

## Executables

- git-tracker (alias)

## Install behavior

- Bottle: not available

## Freshness

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

git-tracker is a Git hook helper for teams that name branches with Pivotal Tracker story numbers. It installs a prepare-commit-msg hook that detects a story ID in the branch name and adds the corresponding Tracker syntax to commit messages.

### Project history

The upstream git_tracker repository was created in 2012 by Steven Harman. Its README presents the tool as GitTracker or git-tracker, a small workflow bridge between local Git branches and Pivotal Tracker's commit-message conventions.

### Adoption history

Adoption appears concentrated around Ruby and macOS/Homebrew users rather than a broad Git ecosystem. The project is published as the git_tracker RubyGem and as the git-tracker Homebrew formula, both pointing back to the same GitHub source repository.

### How it is used

Practitioners install the binary, run `git tracker init` inside each repository where the hook should be active, and include a Pivotal Tracker story number in branch names. On commit, the hook adds a Tracker-formatted story marker, or a keyword such as Fixes with the story number, unless the message already contains the marker.

### Why package nerds care

The package is a compact example of Git's extension culture: a Ruby-distributed tool exposed as a `git tracker` subcommand, with most behavior implemented by installing a standard Git hook into each repository.

### Timeline

- 2012: git_tracker repository created.
- 2.0.0: RubyGems and Homebrew package the tool under git_tracker and git-tracker names.

### Related projects

- git-tracker is tied to Git hooks, Pivotal Tracker's source-control message syntax, RubyGems packaging, and Homebrew distribution.

### Sources

- <https://api.github.com/repos/stevenharman/git_tracker>
- <https://formulae.brew.sh/formula/git-tracker>
- <https://github.com/stevenharman/git_tracker>
- <https://raw.githubusercontent.com/stevenharman/git_tracker/master/README.md>
- <https://rubygems.org/gems/git_tracker>


## Security Notes

narrow executable package without higher-risk signals.

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


## Combined YAML source

View the package source record on GitHub. [combined/git-tracker.yml](https://github.com/mxcl/pkgdb/blob/main/combined/git-tracker.yml)


## Sources

- pkg.so package database
- Geiger risk classifier
- curated package history
- pkgdb category and tag curation
- cross-ecosystem install command graph