Gitignore sensitive files to prevent exposure of sensitive data#5347
Open
blackshady wants to merge 1 commit intokelseyhightower:masterfrom
Open
Gitignore sensitive files to prevent exposure of sensitive data#5347blackshady wants to merge 1 commit intokelseyhightower:masterfrom
blackshady wants to merge 1 commit intokelseyhightower:masterfrom
Conversation
|
LGTM |
| @@ -0,0 +1,2 @@ | |||
| # This is the most effective .gitignore ever! It ignores... nocode. | |||
| !* No newline at end of file | |||
There was a problem hiding this comment.
this leaves your repo vulnerable to contributors committing new code
Suggested change
| !* | |
| * |
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
3 participants
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.
Why?
Exposing sensitive files can compromise the security of the application.
Warning: 🚨
This PR will fail the build. Proceed with caution!
What's next?