chore: untrack .env - #3
Open
CelestialBrain wants to merge 1 commit into
Open
Conversation
.gitignore has listed .env since the initial commit, but the file was already tracked, so the ignore never applied and the working copy has been published on every push since. The values in it are stale local development settings — the JWT_SECRET here was never the one production runs — but a tracked .env invites the next real secret to land in it, which is exactly what happened on the revival branch and was caught only by GitHub push protection. The blob stays in history; removing it there means rewriting a public repo with forks, which is not worth it for dead values. Untracking stops it at HEAD and lets the ignore do its job from here.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
.gitignorehas listed.envsince the initial commit, but the file was already tracked, so the ignore never applied and the working copy has been published on every push since.The values in it are stale local development settings. The
JWT_SECRETin it was never the one production runs, andaccounthas zero rows, so this is not an active auth bypass — but a tracked.envinvites the next real secret to land in it. That is exactly what happened onrevival/m0-unblock, where an OpenAI key was committed and caught only by GitHub push protection.The blob stays in history. Removing it there means rewriting a public repo that has forks, which is not worth it for dead values. Untracking stops it at HEAD and lets the ignore do its job from here.