Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Per-project config file #37

Open
julianhyde opened this issue Sep 3, 2021 · 1 comment
Open

Per-project config file #37

julianhyde opened this issue Sep 3, 2021 · 1 comment

Comments

@julianhyde
Copy link

CLC should look for a config file in the root directory of a project (compare how.travis.yml is used by Travis CI).

Projects should be able to add or remove words and phrases.

For example, I have an issue with flagging 'dummy value'. I know the origin of the word. But it is a term of art, there is no convenient alternative term, and within the software domain it is inoffensive. So my project should be able to exclude it.

A project should be able to 'lock' their word list to a particular version of CLC. We don't want to be broken if CLC upgrades and adds words.

@julianhyde
Copy link
Author

The existence of the config file would also be a convenient way for projects to 'opt in' to checking.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant