Standardize CODEOWNERS and CI/CD governance #5
Conversation
There was a problem hiding this comment.
Pull request overview
This PR establishes code ownership governance by introducing a CODEOWNERS file that defines approval requirements for all repository files and specific ownership for the .github directory.
Key Changes
- Creates a new CODEOWNERS file with two ownership rules: a default rule assigning all files to @FieldControl/shared and a specific rule assigning .github/ directory changes to @FieldControl/codeowners
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| * @FieldControl/shared | ||
|
|
||
| /.github/ @FieldControl/codeowners |
There was a problem hiding this comment.
The CODEOWNERS file should include comments explaining the ownership structure and approval requirements. Consider adding a header comment that describes the purpose of this file and what each ownership rule means. For example, explain that all files by default require approval from the shared team, and that .github directory changes additionally require approval from the codeowners team.
No description provided.