Who is using Codeowners Validator？

[mszostok]

Who is using Codeowners Validator？

I want to sincerely thank everyone who constantly keeps on using and supporting Codeowners Validator! 🚀

This project is developed 100% in my spare time, but I try to keep Codeowners Validator actively developed and maintained.

Reasoning behind this issue

• Find out how many people out there are using this tool to ensure that the time spent on this project is valuable.
• Learn more about the practical usage and be able to prioritize the next step of development. This will impact the v1.0 release. Also, I will be able to note which checks are mostly used and which not.
• Be able to ping users whenever a new version of Codeowners Validator will be released.

Call for action

Add a comment to this issue including the following information:

• GitHub organization
• Link to the repositories where codeowners-validator is used. It doesn't necessarily need to be CI.

[mszostok]

GitHub organization: Microsoft: https://github.com/microsoft

Repositories:

• FluidFramework

[mszostok]

GitHub organization: Node.js https://github.com/nodejs
Repositories:

• node
• node-auto-test

[mszostok]

GitHub organization: .NET Platform https://github.com/dotnet
Repositories:

• Silk.NET

[mszostok]

GitHub organization: Cloud Posse https://github.com/cloudposse
Repositories:

• almost in all > 50

[mszostok]

GitHub organization: iTwin Platform https://github.com/iTwin

Repositories:

• itwinjs-core
• viewer-components-react

[mszostok]

GitHub organization: Magma https://github.com/magma

Repositories:

• magma

[mszostok]

GitHub organization: GloTarAn https://github.com/glotaran

Repositories:

• pyglotaran

[mszostok]

GitHub organization: Square https://github.com/square

Repositories:
-workflow-kotlin

[mszostok]

GitHub organization: gofunky https://github.com/gofunky

Repositories:

• update-codeowners - used as example.

[mszostok]

GitHub organization: Open Ag Technology and Systems Group https://github.com/oats-center

Repositories:

• isoblue-avena

[mszostok]

GitHub organization: island.is https://github.com/island-is
Repositories:

• island.is

[mszostok]

GitHub organization: Code42 Software https://github.com/code42

Repositories:

• dir2consul
• axiomatic

[mszostok]

GitHub organization: Oracle https://github.com/oracle
Repositories:

• graaljs

[mszostok]

GitHub organization: Oppia https://github.com/oppia
Repositories:

• oppia-android

[mszostok]

GitHub organization: Open Ag Data Alliance https://github.com/OADA
Repositories:

• server

[mszostok]

GitHub profile: Vadim https://github.com/rfprod
Repositories:

• flutter_starter
• nx-ng-starter
• mono

[mszostok]

GitHub profile: omrisk https://github.com/omrisk
Repositories:

• clickhouse-playground

[peterdemin]

We use your great tool in Moveworks on git-push as a pre-commit hook.
It's in a private repo. But feel free to ping me.
On a practical note, it would be great to have proper integration with the above pre-commit hook project. That would allow us to manage the version and pass arguments in a consistent fashion with other checks.

[jeremycohen]

We're also looking into using this in a private repo. The main use case we're going after is making sure all files in a test directory have an owner. To do this we may need an additional variable added to only search certain directories for CODEOWNERS, for which I can try putting up a PR.

Also re: pre-commit hook integration that's something that would be beneficial as well!

[julienduchesne]

We use it at Grafana Labs for our private IaC repository. Lots of our CODEOWNERS file is generated so this tool is great to make sure we didn't generate junk!

[jcook-uptycs]

I'm looking into this tool for use in a pre-commit hook, CI and manual use.