tools/git-repo.git/tests/test_project.py, branch v2.72

upload: add --ignore-remote-commits

2026-11-03T08:10:19+00:00

When uploading a branch that merges another remote-tracking branch (such as an upstream branch into the destination branch), ReviewableBranch only excludes the destination tracking branch (^base). As a result, git rev-list walks the merged parent and counts all merged commits even though they already exist on a remote branch, triggering the unusual commit count warning in _VerifyPendingCommits. Add --ignore-remote-commits to `repo upload` to pass --not --remotes to git rev-list in ReviewableBranch so commits already reachable from refs/remotes/* are excluded from the pending commit list. Test: ./run_tests tests/test_project.py tests/test_subcmds_upload.py Change-Id: Ib1fb864982729e20a621144580fe95daa478eaee Reviewed-on: https://gerrit-review.googlesource.com/c/git-repo/+/651284 Tested-by: Romaric Jodin Reviewed-by: Brian Gan Commit-Queue: Romaric Jodin

style: use `import git_refs` everywhere

2026-10-27T09:00:11+00:00

Align with Google style guides and `import git_refs` as a module rather than import symbols out of it. Change-Id: I4e33ebdf3b06acd94494f32cdf39aa58427cd4b2 Reviewed-on: https://gerrit-review.googlesource.com/c/git-repo/+/648703 Reviewed-by: Brian Gan Commit-Queue: Mike Frysinger Tested-by: Mike Frysinger

upload: suppress git push progress when quiet or non-TTY

2026-10-26T21:51:52+00:00

`Project.UploadForReview()` unconditionally passed `--progress` to `git push`, forcing client and remote progress meters (`Counting objects`, `remote: Resolving deltas: 3%..100%`) even on non-TTY stderr or when `-q`/`--quiet` was passed. Meanwhile, `repo upload` ignored `opt.quiet` completely. Move `--progress` injection for `push` into `GitCommand` alongside `fetch` and `clone`, enabling it only when `sys.stderr.isatty()` and none of `--progress`, `--no-progress`, `--quiet`, or `-q` are set. Forward `opt.quiet` from `repo upload` to `Project.UploadForReview()` and pass `--no-progress` to `git push` rather than `--quiet` so Gerrit `remote: https://...` review URLs are still emitted and parsed by `_FindGerritUrls()`. Also suppress the non-error `[OK]` summary banner when `-q`/`--quiet` is set. Bug: 578114287 Change-Id: I88b7b055dcca0db80dae6962886a693fe717c741 Reviewed-on: https://gerrit-review.googlesource.com/c/git-repo/+/649663 Tested-by: Gavin Mak Commit-Queue: Gavin Mak Reviewed-by: Brian Gan

style: use `import git_command` everywhere

2026-10-24T00:00:18+00:00

Align with Google style guides and `import git_command` as a module rather than import symbols out of it. Change-Id: If80d95203e240dd6591e465ef75500c72401d2bf Reviewed-on: https://gerrit-review.googlesource.com/c/git-repo/+/648503 Commit-Queue: Mike Frysinger Reviewed-by: Gavin Mak Tested-by: Mike Frysinger

style: use `import error` everywhere

2026-10-23T00:44:11+00:00

Align with Google style guides and `import error` as a module rather than import classes out of it. Change-Id: I8686fbe7887bd6ceac7a07877af63934f0d0ddd2 Reviewed-on: https://gerrit-review.googlesource.com/c/git-repo/+/647563 Commit-Queue: Mike Frysinger Reviewed-by: Gavin Mak Reviewed-by: Insaf Latypov Tested-by: Mike Frysinger

sync, init: support repo.smartsync config and --head alias

2026-10-21T18:22:58+00:00

Allow users to configure Smart Sync as the default for a checkout: * Add `ManifestProject.smart_sync` backed by `self.config.GetBoolean("repo.smartsync")`. * Add `-s`/`--smart-sync` and `--no-smart-sync`/`--head` to `repo init` to persist `repo.smartsync` in the manifest project config. * Add `--head` as an alias for `--no-smart-sync` in `repo sync` and `repo init`. * Update `Sync._ResolveSmartSyncOption` so `ManifestProject.smart_sync` takes precedence over `` while remaining overridable by per-invocation `repo sync` CLI flags. Bug: 569927750 Test: pytest tests/test_project.py tests/test_subcmds_init.py tests/test_subcmds_sync.py Change-Id: Ib40efc530336efb59a28acfed3d582713e9d67b2 Reviewed-on: https://gerrit-review.googlesource.com/c/git-repo/+/643303 Reviewed-by: Mike Frysinger Commit-Queue: LaMont Jones Tested-by: LaMont Jones

repo: tolerate a transiently missing stable branch

2026-10-13T20:55:40+00:00

The automated release process deletes the stable branch and then recreates it. A client that fetches during that window can't find it: `repo init` fails to resolve --repo-rev, and the daily self-update in `repo sync` fails with "Cannot fetch repo tool". In the launcher, if --repo-rev doesn't resolve after the initial fetch, wait 10 seconds and refetch once before giving up. `resolve_repo_rev` gains a `report_errors` flag so this first check doesn't print an error that the refetch then fixes. Bump the launcher version to 2.69 so existing users pick this up. For fetches of the repo project itself (sync's self-update and `repo selfupdate`), wait 10 seconds instead of 4 before retrying. The delay is now a `RETRY_SLEEP_INITIAL_SEC` class attribute that `RepoProject` overrides, so other projects keep the 4 second delay. This replaces the unused `retry_sleep_initial_sec` parameter of `_RemoteFetch`. Bug: 566270786 Change-Id: I23cb810258522b5aa9eae9d7013dbb7904ebcad8 Reviewed-on: https://gerrit-review.googlesource.com/c/git-repo/+/643265 Tested-by: Brian Gan Commit-Queue: Brian Gan Reviewed-by: Gavin Mak

sync: skip clone.bundle when repo.fetchcmd is configured

2026-10-09T21:09:50+00:00

In Sync_NetworkHalf, clone_bundle defaults to True on initial sync when self.objdir does not exist yet, and _ApplyCloneBundle is called before custom_fetch_configured is checked. For remotes with HTTP/HTTPS URLs that serve /clone.bundle, this causes repo sync to download and unpack the full clone.bundle into .git/objects before invoking repo.fetchcmd. Skip _ApplyCloneBundle when custom_fetch_configured is enabled so repo.fetchcmd exclusively handles object fetching. Bug: 543101585 Change-Id: If41a775a75589ad5a23106163f9932e2940b72d2 Reviewed-on: https://gerrit-review.googlesource.com/c/git-repo/+/641685 Commit-Queue: Gavin Mak Reviewed-by: Brian Gan Tested-by: Gavin Mak

project: peel annotated tags in GetRevisionId with cached refs

2026-10-09T21:09:44+00:00

When all_refs (e.g. self.bare_ref.all in Sync_LocalHalf) is passed to GetRevisionId, looking up a tag ref in all_refs returns the tag object SHA for annotated tags rather than the peeled commit SHA. In Sync_LocalHalf, this causes repo.reprojectcmd to receive a tag SHA in REPO_TREV and DetachHead to fail with 'trying to write non-commit object to branch HEAD', and causes standard checkouts to re-checkout on every subsequent sync because HEAD (the commit SHA) never equals revid (the tag object SHA). Skip the all_refs fast path for refs/tags/* so tags always fall through to bare_git.ResolveCommit, which peels to the underlying commit SHA. Bug: 543101585 Change-Id: Ie4afa3cee9149e2a8438bd8fb4a8026a210848d8 Reviewed-on: https://gerrit-review.googlesource.com/c/git-repo/+/641683 Commit-Queue: Gavin Mak Reviewed-by: Brian Gan Tested-by: Gavin Mak

sync: don't run git ls-remote before fetchcmd on unpinned refs

2026-10-09T21:09:37+00:00

When a project's revision is an unpinned branch or tag and superprojects are not used (so self.revisionId is unset), _CustomFetch previously ran git ls-remote against the Git remote before invoking repo.fetchcmd just to pre-populate REPO_TREV. This added a per-project network round-trip before fetchcmd and forced branch resolution against the Git remote rather than letting fetchcmd resolve REPO_RREV from its own server (just as standard git fetch does in _RemoteFetch). Only populate REPO_TREV before fetchcmd when the target commit SHA is already known (via self.revisionId from superproject or a SHA-pinned revisionExpr). When REPO_RREV is an unpinned branch or tag, leave REPO_TREV empty, let fetchcmd resolve REPO_RREV and update the local tracking ref and FETCH_HEAD, and verify afterward that the tracking ref and FETCH_HEAD resolve to the same valid commit in the object store. Bug: 543101585 Change-Id: I482bf4c022d0e669e5620d4517581ac193983da0 Reviewed-on: https://gerrit-review.googlesource.com/c/git-repo/+/640423 Reviewed-by: Brian Gan Commit-Queue: Gavin Mak Tested-by: Gavin Mak