|.\" DO NOT MODIFY THIS FILE! It was generated by help2man.
|.TH REPO "1" "November 2022" "repo sync" "Repo Manual"
|repo \- repo sync - manual page for repo sync
|Update working tree to the latest revision
|show this help message and exit
|\fB\-j\fR JOBS, \fB\-\-jobs\fR=\fI\,JOBS\/\fR
|number of jobs to run in parallel (default: based on
|number of CPU cores)
|number of network jobs to run in parallel (defaults to
|\fB\-\-jobs\fR or 1)
|number of local checkout jobs to run in parallel
|(defaults to \fB\-\-jobs\fR or 8)
|obsolete option (to be deleted in the future)
|stop syncing after first error is hit
|overwrite an existing git directory if it needs to
|point to a different object directory. WARNING: this
|may cause loss of data
|force remove projects with uncommitted modifications
|if projects no longer exist in the manifest. WARNING:
|this may cause loss of data
|only update working tree, don't fetch
|use the existing manifest checkout as\-is. (do not
|update to the latest revision)
|fetch only, don't update working tree
|detach projects back to manifest revision
|fetch only current branch from server
|fetch all branches from server
|\fB\-m\fR NAME.xml, \fB\-\-manifest\-name\fR=\fI\,NAME\/\fR.xml
|temporary manifest to use for this sync
|enable use of \fI\,/clone.bundle\/\fP on HTTP/HTTPS
|disable use of \fI\,/clone.bundle\/\fP on HTTP/HTTPS
|\fB\-u\fR MANIFEST_SERVER_USERNAME, \fB\-\-manifest\-server\-username\fR=\fI\,MANIFEST_SERVER_USERNAME\/\fR
|username to authenticate with the manifest server
|\fB\-p\fR MANIFEST_SERVER_PASSWORD, \fB\-\-manifest\-server\-password\fR=\fI\,MANIFEST_SERVER_PASSWORD\/\fR
|password to authenticate with the manifest server
|fetch submodules from server
|use the manifest superproject to sync projects;
|disable use of manifest superprojects
|don't fetch tags (default)
|only fetch projects fixed to sha1 if revision does not
|number of times to retry fetches on transient errors
|delete refs that no longer exist on the remote
|do not delete refs that no longer exist on the remote
|run garbage collection on all synced projects
|do not run garbage collection on any projects
|smart sync using manifest from the latest known good
|\fB\-t\fR SMART_TAG, \fB\-\-smart\-tag\fR=\fI\,SMART_TAG\/\fR
|smart sync using manifest from a known tag
|.SS Logging options:
|show all output
|only show errors
|.SS Multi\-manifest options:
|operate starting at the outermost manifest
|do not operate on outer manifests
|only operate on this (sub)manifest
|operate on this manifest and its submanifests
|.SS repo Version options:
|do not verify repo source code
|Run `repo help sync` to view the detailed manual.
|The 'repo sync' command synchronizes local project directories with the remote
|repositories specified in the manifest. If a local project does not yet exist,
|it will clone a new local directory from the remote repository and set up
|tracking branches as specified in the manifest. If the local project already
|exists, 'repo sync' will update the remote branches and rebase any new local
|changes on top of the new remote changes.
|\&'repo sync' will synchronize all projects listed at the command line. Projects
|can be specified either by name, or by a relative or absolute path to the
|project's local directory. If no projects are specified, 'repo sync' will
|synchronize all projects listed in the manifest.
|The \fB\-d\fR/\-\-detach option can be used to switch specified projects back to the
|manifest revision. This option is especially helpful if the project is currently
|on a topic branch, but the manifest revision is temporarily needed.
|The \fB\-s\fR/\-\-smart\-sync option can be used to sync to a known good build as
|specified by the manifest\-server element in the current manifest. The
|\fB\-t\fR/\-\-smart\-tag option is similar and allows you to specify a custom tag/label.
|The \fB\-u\fR/\-\-manifest\-server\-username and \fB\-p\fR/\-\-manifest\-server\-password options can
|be used to specify a username and password to authenticate with the manifest
|server when using the \fB\-s\fR or \fB\-t\fR option.
|If \fB\-u\fR and \fB\-p\fR are not specified when using the \fB\-s\fR or \fB\-t\fR option, 'repo sync' will
|attempt to read authentication credentials for the manifest server from the
|user's .netrc file.
|\&'repo sync' will not use authentication credentials from \fB\-u\fR/\-p or .netrc if the
|manifest server specified in the manifest file already includes credentials.
|By default, all projects will be synced. The \fB\-\-fail\-fast\fR option can be used to
|halt syncing as soon as possible when the first project fails to sync.
|The \fB\-\-force\-sync\fR option can be used to overwrite existing git directories if
|they have previously been linked to a different object directory. WARNING: This
|may cause data to be lost since refs may be removed when overwriting.
|The \fB\-\-force\-remove\-dirty\fR option can be used to remove previously used projects
|with uncommitted changes. WARNING: This may cause data to be lost since
|uncommitted changes may be removed with projects that no longer exist in the
|The \fB\-\-no\-clone\-bundle\fR option disables any attempt to use \fI\,$URL/clone.bundle\/\fP to
|bootstrap a new Git repository from a resumeable bundle file on a content
|delivery network. This may be necessary if there are problems with the local
|Python HTTP client or proxy configuration, but the Git binary works.
|The \fB\-\-fetch\-submodules\fR option enables fetching Git submodules of a project from
|The \fB\-c\fR/\-\-current\-branch option can be used to only fetch objects that are on the
|branch specified by a project's revision.
|The \fB\-\-optimized\-fetch\fR option can be used to only fetch projects that are fixed
|to a sha1 revision if the sha1 revision does not already exist locally.
|The \fB\-\-prune\fR option can be used to remove any refs that no longer exist on the
|The \fB\-\-auto\-gc\fR option can be used to trigger garbage collection on all projects.
|By default, repo does not run garbage collection.
|If at least one project remote URL uses an SSH connection (ssh://, git+ssh://,
|or user@host:path syntax) repo will automatically enable the SSH ControlMaster
|option when connecting to that host. This feature permits other projects in the
|same 'repo sync' session to reuse the same SSH tunnel, saving connection setup
|To disable this behavior on UNIX platforms, set the GIT_SSH environment variable
|to 'ssh'. For example:
|This feature is automatically disabled on Windows, due to the lack of UNIX
|domain socket support.
|This feature is not compatible with url.insteadof rewrites in the user's
|~/.gitconfig. 'repo sync' is currently not able to perform the rewrite early
|enough to establish the ControlMaster tunnel.
|If the remote SSH daemon is Gerrit Code Review, version 2.0.10 or later is
|required to fix a server side protocol bug.