Google Git
Sign in
gerrit/git-repo/c97a306fe7e9493fc3bed034da5e84bcd5f67a41
commit
c97a306fe7e9493fc3bed034da5e84bcd5f67a41
[log]
author
Mike Frysinger <vapier@google.com>
Tue May 12 13:25:09 2026 -0400
committer
Mike Frysinger <vapier@google.com>
Tue May 12 11:50:38 2026 -0700
tree
2d7f9c0d7ad84722a88a303c9e1153bd9450c0e3
parent
5534f164d6aff567f7ea0b5b41e2e5bb35a0212c [diff]
release: update-manpages: revert color filtering

We pull a pinned help2man from cipd now, so we should get stable
behavior between developers.  That means the color filtering should
not be necessary anymore, and we can drop the logic & unittest.

Change-Id: Ib53e1ce7f8d610d7f624c9a019c79dc5f438ac0d
Reviewed-on: https://gerrit-review.googlesource.com/c/git-repo/+/582402
Tested-by: Mike Frysinger <vapier@google.com>
Reviewed-by: Gavin Mak <gavinmak@google.com>
2 files changed
tree: 2d7f9c0d7ad84722a88a303c9e1153bd9450c0e3
  1. .github/
  2. docs/
  3. hooks/
  4. man/
  5. release/
  6. subcmds/
  7. tests/
  8. .flake8
  9. .gitattributes
  10. .gitignore
  11. .gitreview
  12. .mailmap
  13. .project
  14. .pydevproject
  15. cipd_manifest.txt
  16. cipd_manifest.versions
  17. color.py
  18. command.py
  19. completion.bash
  20. completion.zsh
  21. constraints.txt
  22. CONTRIBUTING.md
  23. editor.py
  24. error.py
  25. event_log.py
  26. fetch.py
  27. git_command.py
  28. git_config.py
  29. git_refs.py
  30. git_ssh
  31. git_superproject.py
  32. git_trace2_event_log.py
  33. git_trace2_event_log_base.py
  34. hooks.py
  35. LICENSE
  36. main.py
  37. MANIFEST.in
  38. manifest_xml.py
  39. pager.py
  40. platform_utils.py
  41. platform_utils_win32.py
  42. progress.py
  43. project.py
  44. pyproject.toml
  45. README.md
  46. repo
  47. repo_logging.py
  48. repo_trace.py
  49. requirements.json
  50. run_tests
  51. run_tests.vpython3
  52. run_tests.vpython3.8
  53. setup.py
  54. ssh.py
  55. wrapper.py
README.md

repo

Repo is a tool built on top of Git. Repo helps manage many Git repositories, does the uploads to revision control systems, and automates parts of the development workflow. Repo is not meant to replace Git, only to make it easier to work with Git. The repo command is an executable Python script that you can put anywhere in your path.

Contact

Please use the repo-discuss mailing list or issue tracker for questions.

You can file a new bug report under the “repo” component.

Please do not e-mail individual developers for support. They do not have the bandwidth for it, and often times questions have already been asked on repo-discuss or bugs posted to the issue tracker. So please search those sites first.

Install

Many distros include repo, so you might be able to install from there.

# Debian/Ubuntu.
$ sudo apt-get install repo

# Gentoo.
$ sudo emerge dev-vcs/repo

You can install it manually as well as it's a single script.

$ mkdir -p ~/.bin
$ PATH="${HOME}/.bin:${PATH}"
$ curl https://storage.googleapis.com/git-repo-downloads/repo > ~/.bin/repo
$ chmod a+rx ~/.bin/repo

Shell Completion

Repo includes completion scripts for Bash and Zsh.

Bash

To enable completion in Bash, source completion.bash in your ~/.bashrc:

source /path/to/git-repo/completion.bash

Zsh

To enable completion in Zsh, you can either:

  1. Copy or symlink completion.zsh to a file named _repo in a directory in your $fpath:

    mkdir -p ~/.zsh/completion
# You can copy the file:
cp /path/to/git-repo/completion.zsh ~/.zsh/completion/_repo
# Or symlink it:
ln -s /path/to/git-repo/completion.zsh ~/.zsh/completion/_repo

    Then add that directory to your fpath in ~/.zshrc before compinit:

    fpath=(~/.zsh/completion $fpath)
autoload -Uz compinit
compinit

  2. Or source the file directly and call compdef in your ~/.zshrc:

    source /path/to/git-repo/completion.zsh
compdef _repo repo