project: don't re-shallow manually unshallowed repos during sync If a user has manually unshallowed a repo (e.g. via `git fetch --unshallow`), the absence of the `shallow` file in the gitdir indicates a full clone. Re-applying depth during a subsequent sync would undo the user's intent. Skip re-shallowing in this case by clearing depth when the project is not new and no shallow file is present. Change-Id: I4ee0e78018de9078fe1bd77a9615613ef0c40d33 Reviewed-on: https://gerrit-review.googlesource.com/c/git-repo/+/558743 Reviewed-by: Gavin Mak <gavinmak@google.com> Reviewed-by: Carlos Fernandez <carlosfsanz@meta.com> Reviewed-by: Mike Frysinger <vapier@google.com> Commit-Queue: Lucas Alves <ltanure@gmail.com> Tested-by: Lucas Alves <ltanure@gmail.com> Reviewed-by: Lucas Alves <ltanure@gmail.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