Google Git
Sign in
gerrit / git-repo / 50c6226075258736c3e869242345a59ed7064da4
commit50c6226075258736c3e869242345a59ed7064da4[log] [tgz]
authorKaushik Lingarkar <kaushikl@qti.qualcomm.com>Mon Nov 03 19:58:26 2025 -0800
committerLUCI <gerrit-scoped@luci-project-accounts.iam.gserviceaccount.com>Fri Dec 05 10:35:46 2025 -0800
treec7173b22519ed515e23c386e6a800be5d9603377
parent1e4b2887a760e84f3b453c9caadcae67b701eac9 [diff]
Prevent leftover bare gitdirs after failed sync attempts

The gitdir for a project may be left in a state with bare=true due
to a previous failed sync. In this state, during a subsequent sync
attempt, repo will skip initializing the gitdir (since the directory
already exists) and directly attempt to checkout the worktree, which
will fail because the project is bare. To reduce the chance of this
happening, initialize the gitdir in a temp directory and move it once
it is ready.

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