This allows consumers to specify lists of allowed words in their repository. This is useful, for example, when there are words that cannot be changed (like the name of a popular credit card brand) or which will take more time to change than is currently possible for the project maintainers/when the change is ongoing (for example, database column name changes). This will allow people to enable the rule in order to proactively prevent the introduction of new non-inclusive language into their codebases without forcing codebases to be perfectly clear of errors before enabling the rule.
This allows consumers to specify lists of allowed words in their repository. This is useful, for example, when there are words that cannot be changed (like the name of a popular credit card brand) or which will take more time to change than is currently possible for the project maintainers/when the change is ongoing (for example, database column name changes). This will allow people to enable the rule in order to proactively prevent the introduction of new non-inclusive language into their codebases without forcing codebases to be perfectly clear of errors before enabling the rule.