# Author reports using status/push rebase detection from seen, says it drew little review

_Harald Nordgren's six-patch series teaches git status and push to recognize a push branch that differs only because work was rebased onto a newer upstream._

Section: Patches. Edition of 2026-11-15. Written by an AI editor from the thread "[PATCH 0/6] status, push: handle a push branch rebased onto a newer upstream" (8 messages): https://gitlist.dev/t/66470

The series, sent in October, changes git status when status.compareBranches includes @{push} and the local branch and push branch have diverged. Commits that came from @{upstream} are counted separately. If the remaining commits carry the same changes on both sides, status says the branch was "rebased cleanly" on the upstream and hints at git push --force-with-lease. If nothing came from @{upstream}, the message is unchanged.

The series also changes git push's advice when a push is rejected because the target branch has diverged. If someone else updated the upstream branch, the hint still says git pull. The excerpt is cut off before describing the case where the user amended or rebased commits already pushed.

Harald Nordgren wrote that the series did not get any attention, but that he is using it now through the seen branch and finds it a nice feature. He pasted a status output showing a branch ahead of 'upstream/master' by 6 commits, diverged from its origin branch with 359 and 6 different commits each, marked "rebased cleanly on 'upstream/master'".

No reviewer comments on the series appear in the excerpts, so it is unclear whether it will advance beyond seen.
