acrn-hypervisor/CODEOWNERS
Line: 13: incorrect codeowner user: anthonyzxu Line: 13: incorrect codeowner user: dongyaozu Line: 13: no users/groups matched Line: 15: incorrect codeowner user: anthonyzxu Line: 15: incorrect codeowner user: dongyaozu Line: 15: no users/groups matched Line: 16: incorrect codeowner user: anthonyzxu Line: 16: incorrect codeowner user: dongyaozu Line: 16: no users/groups matched Line: 17: incorrect codeowner user: dbkinder Line: 17: no users/groups matched Line: 19: incorrect codeowner user: dbkinder Line: 19: no users/groups matched
David B. Kinder 656449d0ba devops: Add CODEOWNERS for GitHub review
Seed an initial CODEOWNERS file.  Update as owners for specific areas
are defined.

You can use a CODEOWNERS file to define individuals or teams that are
responsible for code in a repository. The listed names must have write
permissions for the repository.

Code owners are automatically requested for review when someone opens a
pull request that modifies code that they own. When someone with admin
or owner permissions has enabled required reviews, they also can
optionally require approval from a code owner before the author can
merge a pull request in the repository.

Signed-off-by: David B. Kinder <david.b.kinder@intel.com>
2018-05-15 18:03:34 +08:00

20 lines
789 B
Plaintext

# CODEOWNERS for autoreview assigning in github
# File pattern follows the same rules used in .gitignore files,
# Note: doc/ means files in any folder named doc, and its subfolders
# while doc/* means files in any folder named doc, but not its subfolders.
#
# Ordering is important: the last matching pattern takes precedence.
# Put global owners at the top, and detailed reviewers later
#
# Additional reviewers can be assigned manually
# Default/global reviewers (if not overridden later)
* @anthonyzxu @dongyaozu
/hypervisor/ @anthonyzxu @dongyaozu
/devicemodel/ @anthonyzxu @dongyaozu
/doc/ @dbkinder
*.rst @dbkinder