Git Said It Succeeded. The State Said Otherwise.
I keep finding git behaviours the same way: set up the case, run the command, then check the state I actually cared about instead of trusting the success message. Guides pair rerere.enabled with rerere.autoupdate when the second one removes the checkpoint the first one earns you. GitHub reports mergeable while the reviewer is still reading stale bytes. --autosquash prints Successfully rebased and…
Git can appear to succeed, but state may reveal otherwise. The confusion stems from guides recommending rerere.enabled alongside rerere.autoupdate. However, the success message does not always reflect the truth. GitHub may report mergeable while the reviewer is still processing stale data. The --autosquash option can leave a fixup commit in history despite seeming to succeed.
Retargeting a pull request changes the comparison target, not the branch itself. Pinning evidence to a commit, rather than to main, ensures the referenced material remains consistent. Using git worktree instead of stashing allows for preserving untracked files during branch work.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.