[PATCH 2/7] doc: explain fetchRemoteHEADWarn advice
- From
Matt Hunter <m@lfurio.us>
- Date
- Jun 12, 2026, 05:55 UTC
- Message-ID
- <20260612055947.1499497-3-m@lfurio.us>
- In-Reply-To
- <20260612055947.1499497-1-m@lfurio.us>
When the user sets 'remote.<name>.followRemoteHEAD' to 'warn[-if-not-$branch]', git-fetch will report when a fetched HEAD disagrees with the locally-configured remote's HEAD. This additional advice instructs the user how to deal with these warnings, but was previously undocumented in git-config.
Signed-off-by: Matt Hunter <m@lfurio.us> --- Documentation/config/advice.adoc | 4 ++++ 1 file changed, 4 insertions(+)
diff --git a/Documentation/config/advice.adoc b/Documentation/config/advice.adoc index 257db5891817..c3c190ba6a4f 100644 --- a/Documentation/config/advice.adoc +++ b/Documentation/config/advice.adoc @@ -48,6 +48,10 @@ all advice messages. to create a local branch after the fact. diverging:: Shown when a fast-forward is not possible. + fetchRemoteHEADWarn:: + Shown when linkgit:git-fetch[1] reveals that a remote `HEAD` + differs from what is set locally and the user has opted into + receiving a warning in this situation. fetchShowForcedUpdates:: Shown when linkgit:git-fetch[1] takes a long time to calculate forced updates after ref updates, or to warn
-- 2.54.0