chore(security): gitignore the leak-scanner token file#2
Merged
Conversation
The real customer/vendor token list is created by an operator before the tooling that consumes it exists. Without this rule the file sits un-ignored in the working tree and is stageable by `git add -A`, which is precisely the exposure the file exists to prevent. Ignoring the path up front costs nothing.
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
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.
Adds the ignore rule for
scripts/security/scan-tokens.local.txt-- the real customer/vendor token list consumed by the leak scanner.The file is created by an operator before the tooling that references it exists. Without this rule it is an ordinary untracked file and is stageable by
git add -A, which is exactly the exposure it exists to prevent.Only the synthetic
.exampleis ever committed.