Standardize CODEOWNERS and CI/CD governance #2
Conversation
There was a problem hiding this comment.
Pull request overview
This PR establishes code ownership governance by introducing a CODEOWNERS file that defines review requirements for the repository. The configuration sets up a two-tier ownership structure with a default team for general changes and a specialized team for CI/CD infrastructure.
- Adds a CODEOWNERS file with team-based code ownership rules
- Establishes
@FieldControl/sharedas the default owner for all repository files - Designates
@FieldControl/codeownersas the owner for.github/directory changes
💡 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 order of rules in CODEOWNERS matters - GitHub uses the last matching pattern. Currently, the catch-all pattern * @FieldControl/shared on line 1 will be overridden by the more specific /.github/ @FieldControl/codeowners pattern on line 3, which is correct. However, the standard best practice is to place more specific patterns first and the catch-all pattern last. This makes the file easier to read and maintain, as it follows the principle of "specific to general" ordering.
| * @FieldControl/shared | |
| /.github/ @FieldControl/codeowners | |
| /.github/ @FieldControl/codeowners | |
| * @FieldControl/shared |
No description provided.