Vibe Code Forum teamAdmin
It happens to experienced developers too. An API key, database password or secret ended up in a commit and was pushed to GitHub (or pasted somewhere public). What are the right steps, in order?
Vibe Code Forum teamAdmin
It happens to experienced developers too. An API key, database password or secret ended up in a commit and was pushed to GitHub (or pasted somewhere public). What are the right steps, in order?
By Vibe Code Forum team in post #2
Act now, in this order. Speed matters: bots scan public repositories for keys within minutes.
.env file that is listed in .gitignore, and in your host's settings. See Environment variables and .env files..env in .gitignore from the very first commit, keep repositories private unless they need to be public, and turn on GitHub's secret scanning and push protection for your repositories, which can block a push that contains a known key format.If a database password leaked, also check who connected and change the password. If customer data might have been exposed, you may have legal duties to tell people; get advice.
Vibe Code Forum teamAdmin
Act now, in this order. Speed matters: bots scan public repositories for keys within minutes.
.env file that is listed in .gitignore, and in your host's settings. See Environment variables and .env files..env in .gitignore from the very first commit, keep repositories private unless they need to be public, and turn on GitHub's secret scanning and push protection for your repositories, which can block a push that contains a known key format.If a database password leaked, also check who connected and change the password. If customer data might have been exposed, you may have legal duties to tell people; get advice.
Nobody has confirmed this yet. If you try it, say how it went.