tools/git-repo.git, branch stable

sync: Refactor to use _RunOneGC and fix config leakage

2026-04-20T22:34:07+00:00

Extract _RunOneGC to handle GC on a single project. This refactoring makes it easier to invoke GC from parallel worker tasks. Also, avoid modifying the passed-in config dictionary in _RunOneGC by creating a local copy, preventing unintended side effects on other commands sharing the same config. Bug: 498290329 Change-Id: I7b77ed6629b14b5ee3322870b9c6c8ce2bfd6ea2 Reviewed-on: https://gerrit-review.googlesource.com/c/git-repo/+/574923 Reviewed-by: Becky Siegel Tested-by: Gavin Mak Commit-Queue: Gavin Mak

sync: Switch to using self._bloated_projects

2026-04-20T21:07:14+00:00

Store bloated projects in self._bloated_projects and print warnings at the end of execution. This sets up for moving the check to workers. Bug: 498290329 Change-Id: I993f1fd741db2994d480994861588eb18f6c5503 Reviewed-on: https://gerrit-review.googlesource.com/c/git-repo/+/574922 Reviewed-by: Becky Siegel Tested-by: Gavin Mak Commit-Queue: Gavin Mak

tests: Add tests for _CheckForBloatedProjects and _GCProjects

2026-04-20T20:31:41+00:00

Change-Id: I6790a13929b8fc06a3197ca405dedf08d39d54c9 Reviewed-on: https://gerrit-review.googlesource.com/c/git-repo/+/574926 Tested-by: Gavin Mak Reviewed-by: Becky Siegel Commit-Queue: Gavin Mak

upload: Clarify partial sync message on hook failure

2026-04-20T08:52:25+00:00

Demote the partial sync warning from error to info and rephrase it to be a tip rather than an error. This prevents users from thinking that a partial sync is the cause of their hook failures when it is often a linting failure. The message now suggests that a full sync might help if there are cross-project dependencies, instead of implying it will fix any issue. Change-Id: I5d8c52b53ac315aa9f145ed069798bf201fa0815 Reviewed-on: https://gerrit-review.googlesource.com/c/git-repo/+/574262 Tested-by: Marty Heavey Commit-Queue: Marty Heavey Reviewed-by: Gavin Mak

sync: Provide feedback during post-sync operations

2026-04-17T22:47:15+00:00

After the main sync progress bar finishes, there's a pause while some post-sync operations run. Print something to provide feedback so the user doesn't think repo has hung. Bug: 503869525 Change-Id: I695fd560e60dcb394e6844a56c8a336ca1f71c74 Reviewed-on: https://gerrit-review.googlesource.com/c/git-repo/+/574425 Commit-Queue: Gavin Mak Reviewed-by: Becky Siegel Tested-by: Gavin Mak

progress: Ignore updates after progress ends

2026-04-17T22:43:14+00:00

This addresses the occasional "..working.." message at the end of sync. Bug: 503869525 Change-Id: I489d29fa8ae588d77abb7fee5f157800d4abb368 Reviewed-on: https://gerrit-review.googlesource.com/c/git-repo/+/574482 Commit-Queue: Gavin Mak Tested-by: Gavin Mak Reviewed-by: Becky Siegel

project: Avoid skipping fetches for shallow clones without .git/shallow

2026-04-17T16:16:36+00:00

When optimizing fetches for projects with immutable revisions, the fetch should not be skipped if the project is configured for a shallow clone (depth > 0) but the .git/shallow file is missing. The absence of the .git/shallow file means the repository is not a shallow clone, or the shallow clone is incomplete, so a fetch is necessary to ensure the revision is present. Bug: 503081454 Change-Id: Ic3549612bcd69050a926652ee4e522c79ad8124c Reviewed-on: https://gerrit-review.googlesource.com/c/git-repo/+/573821 Tested-by: Becky Siegel Reviewed-by: Gavin Mak Commit-Queue: Becky Siegel

project: Drop --no-deref from update-ref --stdin

2026-04-12T23:39:28+00:00

repo calls `git update-ref --stdin` when updating multiple refs during repo init and repo sync. Historically, `--no-deref` was also passed. Older Git 2.17 which we still support rejects the combination of `--stdin` and `--no-deref`, emitting a usage error even when the stdin input is valid. The `--no-deref` option is only meaningful when updating symbolic refs such as HEAD. The stdin-based update-ref path only operates on explicit refs (tags, remote refs, alternates) and never symbolic refs. Remove the unnecessary option to restore compatibility with Git 2.17 while preserving identical behavior on newer Git versions. Tested with: - Git 2.17.1 - Git 2.34.1 Change-Id: I22001de03800f5699b26a40bc1fb1fec002ed048 Reviewed-on: https://gerrit-review.googlesource.com/c/git-repo/+/571721 Reviewed-by: Mike Frysinger Reviewed-by: Gavin Mak Commit-Queue: Enei Tested-by: Enei

project: implement stateless sync pruning logic

2026-04-09T19:09:40+00:00

Implement in-situ shallow re-fetching and garbage collection logic. Enables repositories with sync-strategy="stateless" to reclaim disk space by running reflog expire and git gc --prune=now if the working tree is clean and has no local commits. Bug: 498730431 Change-Id: I940bdc9b74da29d3f7b13566667dcddea769ebd3 Reviewed-on: https://gerrit-review.googlesource.com/c/git-repo/+/568463 Reviewed-by: Mike Frysinger Tested-by: Gavin Mak Commit-Queue: Gavin Mak

manifest: Add `sync-strategy` attribute to project elements

2026-04-09T19:09:28+00:00

The only supported sync-strategy is "stateless". The intent is to keep the local workspace as small as possible by not keeping history during syncs. This prevents disk space waste for projects with large binaries where we only care about the current version. A follow up change will implement the logic. Bug: 498730431 Change-Id: I84a436a9ca2492893163c6cfda6c28dc62a568f0 Reviewed-on: https://gerrit-review.googlesource.com/c/git-repo/+/568462 Tested-by: Gavin Mak Reviewed-by: Mike Frysinger Commit-Queue: Gavin Mak