Discussion on "Removing a .env file from Git history"

Chris Bongers · 2021-11-10T05:45:16.757Z

I'm sure this happens to everyone sometimes. You accidentally pushed a file with secrets or a password that shouldn't have gotten into the Git history. In the following example, I "accidentally" pushed my .env file to Git simply because I forgot to a...

What's the point in doing this? Regardless of what's in git, the credentials need revoked and git-ignored to prevent in the future. Removing from git history is some extra steps that doesn't really do anything.

Hey Jimmie,

I just like clean repo's. And like I said the env is more a demonstration of a common example.

It might have been another file you wish to remove from the history all together.

Thanks for sharing this. Will be handy someday 😀

Haha, I hope you never have to use it. But that day you do, it's here for you 👋

😂 Chris Bongers.

I've made the mistake once, while I was writing an article and pushing the code to GitHub, I revoked the Key but didn't know about this solution.

This will come in handy when someone else asked me or a colleague makes the mistake.

It's just so nice to know this things exist on your blog 😂

I had to do this a couple of days back. Thank you for this

Happens to everyone.

I've added a small subnote: If you accidentally pushed real-world secrets to a repo, you should always revoke and regenerate them.

Thanks for that, I will definitely keep that in mind.

This is gold, thanks for sharing.

Glad you like it Vishwajeet! 🎉

Search Hashnode

Removing a .env file from Git history

Responses4