diff options
| author | John Bampton <[email protected]> | 2020-12-22 16:09:41 +1000 |
|---|---|---|
| committer | John Bampton <[email protected]> | 2020-12-22 16:09:41 +1000 |
| commit | e96620cd23eb6080c5f3ce6528a274fe6f25af36 (patch) | |
| tree | 0453911da1608ee4b84351bf4c9195310b97808b /CODEOWNERS | |
| parent | 8b2fd45d4639dfd49ea5ec04e7bff378c4c01b6f (diff) | |
| download | mruby-e96620cd23eb6080c5f3ce6528a274fe6f25af36.tar.gz mruby-e96620cd23eb6080c5f3ce6528a274fe6f25af36.zip | |
Create CODEOWNERS file
- You can use a CODEOWNERS file to define individuals or teams that are responsible for code in a repository.
- Code owners are automatically requested for review when someone opens a pull request that modifies code that they own. Code owners are not automatically requested to review draft pull requests.
- https://docs.github.com/en/free-pro-team@latest/github/creating-cloning-and-archiving-repositories/about-code-owners
- This creates a bit more automation so that after you merge this PR, next time someone submits a PR @matz will be automatically assigned as the PR reviewer as CODEOWNER
- CODEOWNERS can even be assigned directories or file types
Diffstat (limited to 'CODEOWNERS')
| -rw-r--r-- | CODEOWNERS | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/CODEOWNERS b/CODEOWNERS new file mode 100644 index 000000000..9f91caaf8 --- /dev/null +++ b/CODEOWNERS @@ -0,0 +1 @@ +* @matz |