This will automate adding reviewers whenever a PR includes changes to the listed files. For now, I've included @OpenAPITools/generator-core-team and my own personal interests in being marked as a reviewer.
If possible, I'd like to use this format in the future for all generator notifications rather than tagging as the 5th TODO item requests, because I find it easier to sort by required reviews vs discussions where I'm tagged.
Please feel free to modify the CODEOWNERS file accordingly. Keep in mind that notifications require the user/team are not "Secret" and have write access to the repository. Assigning a code owner will also display a badge on the file itself in GitHub so users are aware of who "owns" the file.
For more information, see https://help.github.com/en/github/creating-cloning-and-archiving-repositories/about-code-owners
PR checklist
-
Read the contribution guidelines. -
If contributing template-only or documentation-only changes which will change sample output, build the project before. -
Run the shell script(s) under ./bin/(or Windows batch scripts under.\bin\windows) to update Petstore samples related to your fix. This is important, as CI jobs will verify all generator outputs of your HEAD commit, and these must match the expectations made by your contribution. You only need to run./bin/{LANG}-petstore.sh,./bin/openapi3/{LANG}-petstore.shif updating the code or mustache templates for a language ({LANG}) (e.g. php, ruby, python, etc). -
File the PR against the correct branch: master,4.3.x,5.0.x. Default:master. -
Copy the technical committee to review the pull request if your PR is targeting a particular programming language.
cc @OpenAPITools/generator-core-team