Reword the issue comment to use denylist instead of blacklist #745
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.
Changes the comment left on github issues to read:
Which I think is more inclusive than the old message which referred to it as a blacklist. Conveniently, the config file in question doesn't use that term so I don't think it will be confusing to anyone trying to figure out how to drive it.
While making this change crater still uses blacklist a lot internally, but that seemed like kind of a lot for a driveby PR, but if you'd take the patch I'd be happy to switch it out.