📝 Add additional notes about .env and .copier-answers.yml not being in .gitignore by default
#1684
+4
−0
Conversation
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
alejsdev
changed the title
.env and .copier-answers.yml not being in .gitignore by default.env and .copier-answers.yml not being in .gitignore by default
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.
Based on previous discussions (#724, #1119, #383, #218, #128, #122), it's clear that we don't want to go ahead and add files containing secrets (e.g.
.env,.copier-answers.yml) to the template's.gitignoreby default.This PR surfaces that information to the main
README.md. Hopefully, this will help make that decision more visible to those getting started with the project and reduce additional issues/discussions opened on the topic.