project: check upstream ref ancestry for non-shallow clones In _CheckForImmutableRevision, commit d9cc0a15 restricted upstream ref validation strictly to superprojects (if use_superproject) to prevent shallow clones with an upstream attribute from failing ancestry checks and falling back to full clones. However, restricting this check exclusively to superprojects broke non-shallow projects with pinned immutable revisions (such as in Smart Sync, `repo sync -t <BUILD_ID>`, or pinned manifests): When the target commit already exists in the local Git object store (for instance, prefetched into refs/prefetch/ by a background daemon or via shared object dirs), _CheckForImmutableRevision returned True without verifying that the local tracking ref (refs/remotes/<remote>/<upstream>) is present and reaches the revision. As a result, _RemoteFetch skipped fetching the upstream branch, leaving the local tracking ref stale or missing. Subsequent `repo start` branches tracking that remote branch diverged, causing `repo upload` to attempt uploading all intermediate commits between the stale tracking ref and HEAD. Restore upstream ancestry validation in _CheckForImmutableRevision for non-shallow projects when upstream is specified. Also pass the sync depth into _CheckForImmutableRevision call sites so shallow checkouts continue to skip upstream verification and avoid triggering un-shallow fallbacks. Test: PYTHONPATH=. pytest tests/test_project.py Change-Id: Ib5bdf41810bb06c8ed053447209ddc2e488f3913 Reviewed-on: https://gerrit-review.googlesource.com/c/git-repo/+/624361 Tested-by: Rahul Yadav <yadavrah@google.com> Commit-Queue: Rahul Yadav <yadavrah@google.com> Reviewed-by: Gavin Mak <gavinmak@google.com>
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.
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.
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
Repo includes completion scripts for Bash and Zsh.
To enable completion in Bash, source completion.bash in your ~/.bashrc:
source /path/to/git-repo/completion.bash
To enable completion in Zsh, you can either:
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
Or source the file directly and call compdef in your ~/.zshrc:
source /path/to/git-repo/completion.zsh compdef _repo repo