31 lines
965 B
Plaintext
31 lines
965 B
Plaintext
# Setting Up Contribution Guidelines with CODEOWNERS
|
|
|
|
You can create a CODEOWNERS file to define which files require specific approval before changes can be merged. This helps protect critical files in your project.
|
|
|
|
## Steps to implement CODEOWNERS:
|
|
|
|
1. Create a CODEOWNERS file in either the root directory, .github directory, or docs directory
|
|
2. Define file patterns and the users/teams who own those files
|
|
|
|
Here's how to implement it:
|
|
|
|
# CODEOWNERS file defines who needs to approve changes to specific files
|
|
# Format: file-pattern @user-or-team
|
|
|
|
# Dev container configuration
|
|
.devcontainer/* @your-username
|
|
|
|
# Core configuration files
|
|
.vscode/* @your-username
|
|
*.json @your-username
|
|
|
|
# Critical application files that need review
|
|
/src/core/* @your-username @another-team-member
|
|
/services/api/* @api-team-name
|
|
|
|
# Documentation changes can be reviewed by docs team
|
|
/docs/* @docs-team-or-username
|
|
|
|
# Default owners for everything else
|
|
* @default-team-or-username
|