Home/ Questions/Q 7066461
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-28T05:05:06+00:00

I did a commit and reverted with git revert HEAD^ just git log ➜

  • 0

I did a commit and reverted with 

git revert HEAD^

just git log

➜  git:(master) git log
commit 45a0b1371e4705c4f875141232d7a97351f0ed8b
Author: Daniel Palacio <danpal@gmail.com>
Date:   Tue Jan 17 16:32:15 2012 -0800

    Production explanation

But if I do git log –all it still show up. I need to remove it from the history as it has sensitive information

git log --all
commit 5d44355080500ee6518f157c084f519da47b9391
Author: Daniel Palacio
Date:   Tue Jan 17 16:40:48 2012 -0800

    This commit has to be reset

commit 45a0b1371e4705c4f875141232d7a97351f0ed8b
Author: Daniel Palacio 
Date:   Tue Jan 17 16:32:15 2012 -0800

    Production explanation

How do I remove the commit 5d44355080500ee6518f157c084f519da47b9391 from the history too?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    First off, git revert is the wrong command here. That creates a new commit that reverts an older one. That’s not what you’re asking for. Secondly, it looks like you want to revert HEAD instead of HEAD^.

    If you haven’t pushed this anywhere, you can use git reset --hard HEAD^ to throw away the latest commit (this also throws away any uncommitted changes, so be sure you don’t have any you want to save). Assuming you’re ok with the sensitive information being present in your copy and nobody else’s, you’re done. You can continue to work and a subsequent git push won’t push your bad commit.

    If that’s not a safe assumption (though if not I’d love to hear why), then you need to expire your reflogs and force a garbage collection that collects all outstanding objects right now. You can do that with

    git reflog expire --expire=now --expire-unreachable=now --all
git gc --prune=now

    though this should only be done if you really absolutely need to do it.

    If you have pushed your commit, then you’re pretty much out of luck. You can do a force-push to revert it remotely (though only if the remote side allows that), but you can’t delete the commit itself from the remote side’s database, so anyone who has access to that repository can find it if they know what to look for.

    • 0