We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ideally, I would be able to write out an .env file locally, and upon pushing it to github it converts them into secrets.
Then when I pull the repo, it creates/updates the .env file
The text was updated successfully, but these errors were encountered:
This would be a serious security breach. If you upload a .env file, your repository will have your secrets stored in plain text.
.env
Sorry, something went wrong.
No branches or pull requests
Ideally, I would be able to write out an .env file locally, and upon pushing it to github it converts them into secrets.
Then when I pull the repo, it creates/updates the .env file
The text was updated successfully, but these errors were encountered: