Unverified50% confidenceFactExact time
git history split by default moves all local branches derived from the rewritten commit, while --update-refs=head can narrow the scope of the automatic migration to just the single branch currently checked out.
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
10/16/2026
First Seen
Valid until: 1/14/2027
Sources
Related Entities
Related Claims
UnverifiedGit 2.54 introduced the experimental command git history split, which allows users to select content at hunk granularity, write the selected content into a new parent commit, and automatically migrate all local branches built on the old commit onto the rewritten history.75% similarVerifiedGitHub dynamically generates a temporary merge commit (refs/pull/*/merge) on the server side for each PR, which must be explicitly fetched via git fetch and does not exist in a normal git clone result.73% similarUnverifiedIf modifications are pushed to a remote Git branch, all collaborators must force-sync; otherwise, history will diverge.72% similarUnverifiedThe git rebase --update-refs command introduced in Git 2.38 automatically updates all intermediate branch references encountered during a rebase, simplifying rebase operations on stacked branches.71% similarUnverifiedgit filter-branch and git filter-repo can batch-rewrite commit content (commit messages, authors, timestamps, etc.), recalculating the hash values of all affected commits and producing an entirely new chain parallel to the original history.70% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1046578API
curl https://kongchang.com/api/v1/knowledge/claims/1046578MCP
get_claim(id=1046578)