Update CODEOWNERS

[mmkay]

No description provided.

[lucabello]

Interesting that it fails unit tests; the inclusive naming thing is also weird, because the error I see is:

Error: Unable to resolve action. Repository not found: canonical-web-and-design/Inclusive-naming

The repo is reachable and public; also, the workflow is the same we use for our charm quality checks

[mmkay]

@lucabello I fixed the unit tests - it looks like the error message in validation that was tested changed to contain file path. The inclusive naming check is, however, weirder. I see that there was a path change and inclusive naming seems to be now directly in canonical org but redirects work. I wonder if the issue isn't related to the repo we're in being private.

@simskij any ideas?

[simskij]

I can file a request with IS to make it internal if y'all think that might make a difference?

[mmkay]

@simskij - although it certainly won't hurt, I think it might be better to fix the underlying redirect. On it :)