Mateusz Szostok

Hi @udayrajMT The idea sounds interesting. I will try to investigate if the GitHub CODEOWNERS and the Gitlab ones have the same syntax expression as currently, the codeowners-validator validates a...

Hi @klauern thanks for that suggestion. I also think that cobra is quite overkilling but it provides autocompletion, generating documentation from code etc., working with the configuration from different sources...

Hi @remal Unfortunately, the Codeowners Validator works properly in repos which are under organization. For now, you can disable the `owners` checker. Example: ```yaml name: 'Codeowners validation' on: push: paths:...

connected with https://github.com/mszostok/codeowners-validator/issues/73

Hi @ZacSweers the GitHub token was already described some time ago here: https://github.com/mszostok/codeowners-validator/blob/master/docs/gh-token.md Regarding the endpoint problem that you mentioned. I'm using the endpoint under the repos URL as I...

Hi @Nuru I can add opt to disable that e.g. `OWNER_CHECKER_DISABLE_ORG_MEMBER_VALIDATION=true/false`. But it will be a short-term solution. Later someone else can as about disabling other _sub-check_, maybe even disable...

Hi @peterdemin and @jeremycohen! You both posted that the pre-commit support would be nice to see in codeowners-validator. Do you already have snippets on how you use it with pre-commit?...

the problem is that in current approach we are checking team permission entry which is out-dated > It no longer identifies thepermission a team has on its repos, but only...

Probably the best option is to use the GraphQL query to remove the overfetching problme, example query: ```graphql { organization(login: "gh-codeowners") { teams(first: 2) { pageInfo { hasNextPage } nodes...

This issue was solved by #62. I do not close it because we can recheck if it is worth to change the implemented logic from REST to GraphQL. More context:...