It is only an issue if you have only published (pushed) some of your commits, because they would be harder to merge to other repos which have already those commits. Since their SHA1 have changed, Git would try to replay them again on those repos. If you have not (pushed any of those commits again), … Read more
2022: I described last August in “Git interactive rebase: how to move other branches (refs) automatically?” a new rebase option –update-ref (Git 2.38, Q3 2022): Automatically force-update any branches that point to commits that are being rebased. Any branches that are checked out in a worktree are not updated in this way. branch1 branch2 | … Read more
According to git’s Object Model if you only change the meta-data of a commit (i.e. commit message) but not the underlying data (“tree(s)”) contained within it then it’s Tree hash will remain unchanged. Aside from editing a commit message, you are also performing a rebase, which will change the Tree hashes of each commit in … Read more
To understand this, we need to understand a bit about how git works. A git repository is a tree structure, where the nodes of the tree are commits. Here’s an example of a very simple repository: it has four commits on the master branch, and each commit has an ID (in this case, a, b, … Read more
Make sure your working tree is clean, then git reset –soft HEAD~3 git commit -m ‘new commit message’
You can avoid using the –onto parameter by making a temp branch on the commit you like and then use rebase in its simple form: git branch temp master^ git checkout topic git rebase temp git branch -d temp
TL;DR answer: GIT_SEQUENCE_EDITOR=: git rebase -i HEAD~3 You can’t stop git rebase –interactive from running the “sequence editor” (that’s the edit command on the “sequence file” containing the various pick, etc., commands). However, if you examine the interactive rebase script: $ vim $(git –exec-path)/git-rebase–interactive you’ll find code like this near line 230 or so: git_sequence_editor … Read more
If A and B are not the same repo (you created B by using the latest working copy you had), you have to use a graft to pretend that they have common history. Let’s assume you’ve added A as a remote for B as per VonC’s answer, and the repo looks like this1: ~/B$ git … Read more
I saw this still here so I figured I might as well answer the question. So the answer is YES. It will remove the contributions from the graph. It won’t do it right away because commits that are no longer being pointed to by anything can technically still be reached for awhile but are eventually … Read more
I’ve managed to work around this by: Locate the last commit that retained the order Run git rebase -i <hash of that commit> Replace all pick with reword Run git push -f Before that, I tried changing only the first commit message, which also changes all the following hashes, but that didn’t fix it. I … Read more