tools/git-repo.git/completion.zsh, branch stable

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

config: add subcommand to manage ~/.repoconfig/config

2026-10-22T15:34:46+00:00

Per-user settings such as sync.smartsync live in ~/.repoconfig/config, but reading or changing them required knowing the file location and running `git config --file ~/.repoconfig/config ...`. Add `repo config` as a thin wrapper around RepoConfig.ForUser(), following the subcommand style of modern `git config`: * `repo config get ` prints the value(s), exiting 1 if unset. * `repo config set ` sets it. * `repo config unset ` removes it; a missing key is a no-op. * `repo config list` shows all settings. Values are stored as strings; `--type=bool|int` validates and canonicalizes them on set and get, like `git config --type`. `-z` makes get and list NUL-terminated for scripting. Setting names are validated by `git config` itself when writing. Factor the value parsing out of GitConfig.GetBoolean()/GetInt() into ParseBoolean()/ParseInt() so the command and the readers agree, and accept on/off/1/0 as booleans like git does. Only the per-user file is handled; per-checkout settings in .repo/manifests.git/config are out of scope. Like other subcommands, it runs from inside a repo checkout. Update docs/repoconfig.md to use the new command in its examples and add zsh completion and the man page. Bug: 569927750 Test: ./run_tests Change-Id: I940d0318549fe9d79f6f9173139f0b96a706f1bf Reviewed-on: https://gerrit-review.googlesource.com/c/git-repo/+/645727 Reviewed-by: Mike Frysinger Tested-by: Insaf Latypov Commit-Queue: Insaf Latypov

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

sync: Support manifest-driven default smart sync

2026-10-01T10:13:33+00:00

Add support for enabling smart sync by default via the sync-smartsync="true" attribute on the manifest element. When sync-smartsync is set to true in the manifest defaults: - Plain `repo sync` triggers Smart Sync automatically. - If that implicit Smart Sync fails (manifest server unreachable, or the returned manifest cannot be parsed), repo silently falls back to a regular ToT sync. The reason is logged with --verbose. - `--no-smart-sync` CLI flag overrides the manifest default and syncs to ToT. - Passing explicit `-s` / `--smart-sync` forces Smart Sync as before, and its failures are still fatal. - `-t`, `--smart-tag`, `-m`, `--manifest-name`, and `--superproject-revision` disable the default smart sync. - `-l` / `--local-only` and `--no-manifest-update` skip the manifest server and reuse the existing smart_sync_override.xml, if any. Update docs, completion, regenerate man pages, and add tests for XML parsing, serialization, CLI option resolution, and the fallback and reuse paths. Bug: 545137090 Change-Id: If75569c58dd525d170e9801e70ccbf02206a52f2 Reviewed-on: https://gerrit-review.googlesource.com/c/git-repo/+/617641 Tested-by: Rahul Yadav Commit-Queue: Rahul Yadav Reviewed-by: Gavin Mak

hooks: add --fix option to auto-apply hook fixes

2026-08-27T10:28:58+00:00

Pass the --fix flag as a keyword argument "fix" to the hook main function. This allows hooks (such as git-repohooks) to decouple automated fix application from the -y/--yes flag so that -y can answer yes to upload confirmation prompts without triggering file mutations. Companion change in git-repohooks: https://gerrit-review.googlesource.com/c/git-repohooks/+/621761 Bug: 546510319 Test: python3 -m pytest tests/test_hooks.py Change-Id: If0288d4791fc0a2aba6e88854e3aa81b0923b664 Reviewed-on: https://gerrit-review.googlesource.com/c/git-repo/+/619281 Commit-Queue: Rahul Yadav Tested-by: Rahul Yadav Reviewed-by: Gavin Mak

sync: Deprecate fetch-submodules flag names

2026-07-21T07:19:21+00:00

The names for flags --fetch-submodules / --no-fetch-submodules are misleading, since they impact the full sync operation (fetch and checkout), not just the fetching. Introduce new flags --recurse-submodules / --no-recurse-submodules and treat the old ones as deprecated aliases. Change-Id: I78339a3e0496a855c222c1869b27b578507886a7 Reviewed-on: https://gerrit-review.googlesource.com/c/git-repo/+/608881 Commit-Queue: Josef Malmstrom Reviewed-by: Gavin Mak Reviewed-by: Mike Frysinger Tested-by: Josef Malmstrom

sync: Add CLI flag for globally disabling submodule fetch

2026-07-16T08:19:51+00:00

A global setting for disabling fetching of submodules is useful since this can currently otherwise only be done by modifying the manifest, or by explicitly providing projects on command line. Add this setting as --no-fetch-submodules to mirror the existing --fetch-submodules. Change-Id: Ic727c54f11a594aa52315751284b87138cf246bb Reviewed-on: https://gerrit-review.googlesource.com/c/git-repo/+/607641 Commit-Queue: Josef Malmstrom Reviewed-by: Gavin Mak Tested-by: Josef Malmstrom Reviewed-by: Mike Frysinger

Add zsh completion

2026-05-08T14:46:00+00:00

This PR adds `completion.zsh` to allow for relatively intelligent completion of `repo` command-line arguments for all commands of the `repo` CLI. The `completion.zsh` can be added to your zsh completions by copying (and renaming) the completion script to a directory that you have added to your zsh completion path. ``` cp completion.zsh $ZSH_COMPLETION_DIRECTORY/_repo ``` You must name the file `_repo` for it to register as completion for `repo`. You can add a directory to your zsh completion by updating your `fpath` variable before calling `compinit` as follows: ``` fpath=( /path/to/zsh-completions/dir $fpath ) ``` Future work: Generate this file using the subcommand classes and python reflection. Change-Id: I6a4e785c1efcf9076bd693976ac03578836b691b Reviewed-on: https://gerrit-review.googlesource.com/c/git-repo/+/579561 Commit-Queue: Mike Frysinger Reviewed-by: Gavin Mak Tested-by: Kamal Sacranie Reviewed-by: Mike Frysinger