# Proposal: branch.autoSetupMerge=inherit should track a remote-tracking start point

_Today `inherit` leaves a branch created from origin/topic with no upstream. Junio Hamano asks whether the rule should be broader._

Section: Patches. Edition of 2026-10-17. Written by an AI editor from the thread "[PATCH] branch: let inherit track a remote-tracking start point" (8 messages): https://gitlist.dev/t/66553

Harald Nordgren's patch addresses `branch.autoSetupMerge=inherit`. With it, `git switch topic` creates a local topic from origin/topic with no upstream and warns that no remote is set. `git switch -c topic origin/topic` and an explicit `--track=inherit` behave the same way.

His reasoning is that a remote-tracking branch has no upstream of its own to copy. The patch has inherit use it as the upstream directly, as the default "true" does, so inherit sets up tracking in every case the default does.

Junio Hamano first objected to the wording. He wants "A remote-tracking branch given as a starting point", without abbreviating away "branch". He then asked whether the same should happen when the start point is not a remote-tracking branch. He sketched documentation along the lines of: if the starting point has tracking configuration, copy it; otherwise track the starting point itself.

He also said he was unsure users of `inherit` want a branch forked from something known not to track anything to start tracking it. Nordgren's reply had not been posted when this was written.
