Adding .env files to .gitignore #4
Merged
Conversation
This file contains 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
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.
Convention dictates that one should not commit .env files to git. Have added .env* files to
.gitignore. If a user wants to document the types of environment variables required for a repo, asample.envfile with documentation for which variables to set is advised.Pull Request type
Please check the type of change your PR introduces:
What is the current behavior?
Currently .env files are being committed to git.
What is the new behavior?
.gitignorenow defaults to correct standards discouraging users from committing .env files to git.Does this introduce a breaking change?