Use usernames as codeowners for venvironment schemas

[raphael-grimm]

(as suggested in #4190)

[github-actions]

Thanks for the PR!

This section of the codebase is owned by @madskristensen and @hyperupcall - if they write a comment saying "LGTM" then it will be merged.

[raphael-grimm]

@hyperupcall seems to have the same / a similar issue with usernames.

Unknown owner on line 30: make sure @raphael-grimm exists and has write access to the repository
…t-* @vectorgrp/canoe-ci-tools @raphael-grimm @JoergSrj

Since I don't have write permissions on this repo I can't be codeowner

[hyperupcall]

Thanks for the followup PR!.

For the error shown by GitHub, GitHub's CODEOWNER linter is giving a false positive (for our use case). Instead of giving managing code owners through GitHub directly, we use the code-owner-self-merge action because it's more flexible and customizable. That action itself parses the CODEOWNERS file, does the @mentions, and merges the PRs (when a "codeowner" replies @lgtm). So even if GitHub prints a linting error, you should still be able to use the bot/action fully. More info available about the bot is in CONTRIBUTING.md

[raphael-grimm]

@hyperupcall ok, understood. Are there any changes i should do to this branch?

[hyperupcall]

Nope, thank you