git-reviewers
Intelligently find code reviewers. See also, git-browse.
Installation
Homebrew (preferred for MacOS)
If you use Homebrew, you can install git-reviewers through the homebrew-albertyw tap:
brew install albertyw/albertyw/git-reviewers
Manual
If you don't use Homebrew, first clone this repository to somewhere on your system
(perhaps in your dotfiles
repository), then run <REPOSITORY_LOCATION>/install.sh.
After installation, you can modify any default flags for git-reviewers
in ~/.gitconfig
Usage
usage: reviewers.py [-h] [-v] [--verbose] [-i IGNORE] [-j JSON] [-c]
Suggest reviewers for your diff. https://github.com/albertyw/git-reviewers
optional arguments:
-h, --help show this help message and exit
-v, --version show program's version number and exit
--verbose verbose mode
-i IGNORE, --ignore IGNORE
ignore a list of reviewers (comma separated)
-j JSON, --json JSON json file to read configs from, overridden by CLI
flags
-c, --copy Copy the list of reviewers to clipboard, if available
-b BASE_BRANCH, --base-branch BASE_BRANCH
Compare against a base branch (default: master)
Finders
git-reviewers is componsed of a set of strategies for generating lists of
reviewers, or Finders. They return a weighted set of reviewers which is then
sorted and recommended to you. They include:
FindLogReviewers- Generate a list of reviewers based on committers to your committed (but not merged with master) filesFindHistoricalReviewers- Generate reviewers based on the repository committers as a wholeFindArcCommitReviewers- Generate reviewers based on arc commit messages for files which you have modified on your branch
Configuration
git-reviewers supports reading configuration from a configuration file
with the --json flag. The configuration file accepts json with the
following fields (all fields optional):
{
"verbose": false,
"copy": false,
"ignore": ["a", "b", "c"],
"base_branch": "master"
}
git-reviewers will also by default search for and load a json
configuration file at ~/.git/reviewers.
Development
pip install -e .[test]
ruff check .
mypy .
coverage run -m unittest
coverage report -m
Publishing
pip install twine
python -m build
twine upload dist/*
Need to also update albertyw/homebrew-albertyw.
Metadata
Release files for git-reviewers 0.13.8
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| git_reviewers-0.13.8.tar.gz | 8.6 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| git_reviewers-0.13.8-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 16.2 kB
Release files / git_reviewers-0.13.8.tar.gz
| Download URL | git_reviewers-0.13.8.tar.gz |
|---|---|
| Size | 8.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0f9f45fc845b12ee6cc8ddc10c92b9383b64c8eac68f8a291ba42909f8652552
|
|
BLAKE2b-256 checksum How to use checksums |
0b23e6b2f697c61a0a4972770eee3428e019128bd54617b5d97c90acc1c48d3f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 26, 2026.
Transparency logRelease files / git_reviewers-0.13.8-py3-none-any.whl
| Download URL | git_reviewers-0.13.8-py3-none-any.whl |
|---|---|
| Size | 7.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6e47f3760d6cad48f3476209f421f34761219a6e555fe6d7771e017c8ed62dee
|
|
BLAKE2b-256 checksum How to use checksums |
511ba4dfbd30cba6473cfd40e1c050a904753086c090fef0878deae6946f7fee
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 26, 2026.
Transparency log