The inclusive naming check on e..g this PR is failing with:
Raw Output:
Warning: settes/TestRoutes.test_blog_date_notice.yaml:462:557: [warning] `master` may be insensitive, use `primary`, `main` instead
Error: [Inclusive naming check] reported by reviewdog 🐶
Warning: `MASTER` may be insensitive, use `primary`, `main` instead
This is because the contents of blog articles that we're testing against contain URLs and references to repositories that still use "master" as a main branch. I don't think it's feasible to change this to make the checker happy.
It would generally make sense to exclude automatically retrieved API responses, which are mainly only meant to be read by the test library anyway, from the checker. But I couldn't see an easy way to do this from reading the ReviewDog README.
The inclusive naming check on e..g this PR is failing with:
This is because the contents of blog articles that we're testing against contain URLs and references to repositories that still use "master" as a main branch. I don't think it's feasible to change this to make the checker happy.
It would generally make sense to exclude automatically retrieved API responses, which are mainly only meant to be read by the test library anyway, from the checker. But I couldn't see an easy way to do this from reading the ReviewDog README.