tree 1eb7ca19dc8184f80770b49e45672c591c01386a
parent 0176586544d36d2902d6b8442ea4dc78e7921b8e
author Lucas Tanure <ltanure@gmail.com> 1772874945 +0000
committer LUCI <gerrit-scoped@luci-project-accounts.iam.gserviceaccount.com> 1774026520 -0700

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>