Cursor uploads .env file with secrets despite .gitignore and .cursorignore
1–10 of 22 posts
Re: Cursor uploads .env file with secrets despite .gitignore and .cursorignore
#2Re: Cursor uploads .env file with secrets despite .gitignore and .cursorignore
#3Re: Cursor uploads .env file with secrets despite .gitignore and .cursorignore
#4but yeah there should be some commit hook that rejects a commit like this for obvious non starters like a .env or credentials.yaml or something (UNLESS the dev explicitly goes and toggles that setting to be off)
Re: Cursor uploads .env file with secrets despite .gitignore and .cursorignore
#5how can it upload a .env when its there in .gitignore? even if you go and remove the entry of .env from .gitignore, it doesn't start getting tracked right? but yeah there should be some commit hook that rejects a commit like this for obvious non starters like a .env or credentials.yaml or something (UNLESS the dev explicitly goes and toggles that setting to be off)
Regardless of whether it actually makes a commit with the secret, it's still being leaked.
Re: Cursor uploads .env file with secrets despite .gitignore and .cursorignore
#6how can it upload a .env when its there in .gitignore? even if you go and remove the entry of .env from .gitignore, it doesn't start getting tracked right? but yeah there should be some commit hook that rejects a commit like this for obvious non starters like a .env or credentials.yaml or something (UNLESS the dev explicitly goes and toggles that setting to be off)
Re: Cursor uploads .env file with secrets despite .gitignore and .cursorignore
#7Re: Cursor uploads .env file with secrets despite .gitignore and .cursorignore
#8pro-tip: don't use .env files. They're a hack anyway.