# followRemoteHEAD validation patch waits on hn/fetch-refmap

_The change would stop unrelated commands such as `git push` from warning about a bad remote.<name>.followRemoteHEAD value._

Section: Patches. Edition of 2026-11-09. Written by an AI editor from the thread "[PATCH v1] remote.c: defer remote.<name>.followRemoteHEAD validation" (19 messages): https://gitlist.dev/t/66581

Colin Hinton's patch continues 86129fd, which deferred validation of fetch.followRemoteHEAD. The per-remote setting is still validated in handle_config(), so any command that loads remote configuration, such as `git push` or `git remote -v`, warns even though only `git fetch` uses the value.

The patch stores the raw string in struct remote and resolves it lazily in do_fetch() via get_follow_remote_head(). It removes the parsed follow_remote_head and no_warn_branch members and the NEEDSWORK comment from 86129fd, and `git remote set-head` compares against the raw string.

Hinton said he prefers Matt Hunter's approach as cleaner and simpler because it removes the setup at the call site, and will credit Hunter. He is delaying the re-roll until hn/fetch-refmap is in 'next' so he can resolve conflicts himself, and asked Junio Hamano whether a better base branch exists.
