Home Explore Blog CI



git

2nd chunk of `Documentation/config/remote.adoc`
d28696dfbcc26f62fdd0f6ab8bc37fb748bbd695c977c38e0000000100000e35
 will automatically behave
	as if the `--mirror` option was given on the command line.

remote.<name>.skipDefaultUpdate::
	A deprecated synonym to `remote.<name>.skipFetchAll` (if
	both are set in the configuration files with different
	values, the value of the last occurrence will be used).

remote.<name>.skipFetchAll::
	If true, this remote will be skipped when updating
	using linkgit:git-fetch[1], the `update` subcommand of
	linkgit:git-remote[1], and ignored by the prefetch task
	of `git maintenance`.

remote.<name>.receivepack::
	The default program to execute on the remote side when pushing.  See
	option --receive-pack of linkgit:git-push[1].

remote.<name>.uploadpack::
	The default program to execute on the remote side when fetching.  See
	option --upload-pack of linkgit:git-fetch-pack[1].

remote.<name>.tagOpt::
	Setting this value to --no-tags disables automatic tag following when
	fetching from remote <name>. Setting it to --tags will fetch every
	tag from remote <name>, even if they are not reachable from remote
	branch heads. Passing these flags directly to linkgit:git-fetch[1] can
	override this setting. See options --tags and --no-tags of
	linkgit:git-fetch[1].

remote.<name>.vcs::
	Setting this to a value <vcs> will cause Git to interact with
	the remote with the git-remote-<vcs> helper.

remote.<name>.prune::
	When set to true, fetching from this remote by default will also
	remove any remote-tracking references that no longer exist on the
	remote (as if the `--prune` option was given on the command line).
	Overrides `fetch.prune` settings, if any.

remote.<name>.pruneTags::
	When set to true, fetching from this remote by default will also
	remove any local tags that no longer exist on the remote if pruning
	is activated in general via `remote.<name>.prune`, `fetch.prune` or
	`--prune`. Overrides `fetch.pruneTags` settings, if any.
+
See also `remote.<name>.prune` and the PRUNING section of
linkgit:git-fetch[1].

remote.<name>.promisor::
	When set to true, this remote will be used to fetch promisor
	objects.

remote.<name>.partialclonefilter::
	The filter that will be applied when fetching from this	promisor remote.
	Changing or clearing this value will only affect fetches for new commits.
	To fetch associated objects for commits already present in the local object
	database, use the `--refetch` option of linkgit:git-fetch[1].

remote.<name>.serverOption::
	The default set of server options used when fetching from this remote.
	These server options can be overridden by the `--server-option=` command
	line arguments.
+
This is a multi-valued variable, and an empty value can be used in a higher
priority configuration file (e.g. `.git/config` in a repository) to clear
the values inherited from a lower priority configuration files (e.g.
`$HOME/.gitconfig`).

remote.<name>.followRemoteHEAD::
	How linkgit:git-fetch[1] should handle updates to `remotes/<name>/HEAD`
	when fetching using the configured refspecs of a remote.
	The default value is "create", which will create `remotes/<name>/HEAD`
	if it exists on the remote, but not locally; this will not touch an
	already existing local reference. Setting it to "warn" will print
	a message if the remote has a different value than the local one;
	in case there is no local reference, it behaves like "create".
	A variant on "warn" is "warn-if-not-$branch", which behaves like
	"warn", but if `HEAD` on the remote is `$branch` it will be silent.
	Setting it to "always" will silently update `remotes/<name>/HEAD` to
	the value on the remote.  Finally, setting it to "never" will never
	change or create the local reference.

Title: Git Remote Repository Configuration Options
Summary
This section continues to describe various configuration options for Git remote repositories, including settings for pruning, tag management, promisor objects, partial clone filtering, server options, and handling updates to the remote HEAD reference.