Update anonymize.config.json with a declarative "I've modified this file" entry#516
Merged
Update anonymize.config.json with a declarative "I've modified this file" entry#516
Conversation
Introduce a initial "comment" entry to "declare" that an anonymizer config has been validated for a given project setup. This allows for automated tools to check the validity of the file.
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
2 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.
The anonymizer config is an important tool in staying compliant with privacy regulations in relation to development work, and as such it is important to never trust the default.
Of course, this is hard when there's a rather reliable default provided, and it is easy to become complacent and just expect the best.
This PR introduce a initial "comment" entry to the anonymizer config file, which has the intent to "declare" that a config has been validated for a given project setup.
By introducing this line, it is also possible to say "the default is OK", and without making modifications to the configs them selves, and still allow for automation in detecting projects where this has been missed.