Change first commit of project with Git? [duplicate]

by

As mentioned by ecdpalma below, git 1.7.12+ (August 2012) has enhanced the option --root for git rebase:

“git rebase [-i] --root $tip” can now be used to rewrite all the history leading to “$tip” down to the root commit.

That new behavior was initially discussed here:

I personally think “git rebase -i --root” should be made to just work without requiring “--onto” and let you “edit” even the first one in the history.
It is understandable that nobody bothered, as people are a lot less often rewriting near the very beginning of the history than otherwise.

The patch followed.

(original answer, February 2010)

As mentioned in the Git FAQ (and this SO question), the idea is:

  1. Create new temporary branch
  2. Rewind it to the commit you want to change using git reset --hard
  3. Change that commit (it would be top of current HEAD, and you can modify the content of any file)

  4. Rebase branch on top of changed commit, using:

    git rebase --onto <tmp branch> <commit after changed> <branch>`

The trick is to be sure the information you want to remove is not reintroduced by a later commit somewhere else in your file. If you suspect that, then you have to use filter-branch --tree-filter to make sure the content of that file does not contain in any commit the sensible information.

In both cases, you end up rewriting the SHA1 of every commit, so be careful if you have already published the branch you are modifying the contents of. You probably shouldn’t do it unless your project isn’t yet public and other people haven’t based work off the commits you’re about to rewrite.

More Related Contents:

  1. Remove sensitive files and their commits from Git history
  2. How do you fix a bad merge, and replay your good commits onto a fixed merge?
  3. What’s the difference between ‘git merge’ and ‘git rebase’?
  4. git rebase, keeping track of ‘local’ and ‘remote’
  5. How to substitute text from files in git history?
  6. How do I recover/resynchronise after someone pushes a rebase or a reset to a published branch?
  7. git cherry-pick says “…38c74d is a merge but no -m option was given”
  8. Completely remove files from Git repo and remote on GitHub
  9. How to rebase many branches (with the same base commit) at once?
  10. How can I move a directory in a Git repo for all commits?
  11. git rebase and git push: non-fast forward, why use?
  12. Git push rejected “non-fast-forward”
  13. Split large Git repository into many smaller ones
  14. git pull –rebase lost commits after coworker’s git push –force
  15. How do I use `git rebase -i` after `git merge` without messing things up?
  16. Change old commit message using `git rebase`
  17. How do I run a code formatter over my source without modifying git history?
  18. How to rebase one Git repository onto another one?
  19. Could I change my name and surname in all previous commits?
  20. Is there a way to squash a number of commits non-interactively?
  21. Rebasing and what does one mean by rebasing pushed commits
  22. How can I rewrite history so that all files, except the ones I already moved, are in a subdirectory?
  23. How to extract one file with commit history from a Git repo with index-filter & co?
  24. Update a development team with rewritten Git repo history, removing big files
  25. Running filter-branch over a range of commits
  26. Why has git-filter-branch not rewritten tags?
  27. Rewrite history git filter-branch create / split into submodules / subprojects
  28. Can tags be automatically moved after a git filter-branch and rebase?
  29. git rm – fatal: pathspec did not match any files
  30. Git – remove commits with empty changeset using filter-branch

Leave a Comment