|
| 1 | +title: |
| 2 | + # Regex pattern to match against PR title |
| 3 | + # Example: Conventional Commits format |
| 4 | + pattern: "^(feat|fix|docs|chore|refactor|test|style|perf|ci|build|revert):" |
| 5 | + |
| 6 | + # Minimum length of the title |
| 7 | + min_length: 10 |
| 8 | + |
| 9 | + # Maximum length of the title (optional) |
| 10 | + # max_length: 100 |
| 11 | + |
| 12 | +# Label validation rules |
| 13 | +labels: |
| 14 | + # List of required labels |
| 15 | + # All labels in this list must be present on the PR |
| 16 | + required: |
| 17 | + # Type/Kind labels - Required: at least one type label |
| 18 | + # Common types: bug, feature, enhancement, documentation, refactor, test, chore |
| 19 | + - "kind/bug" # Bug fixes |
| 20 | + - "kind/feature" # New features |
| 21 | + - "kind/docs" # Documentation changes |
| 22 | + - "kind/enhancement" # Feature enhancements/improvements |
| 23 | + - "kind/refactor" # Code refactoring |
| 24 | + - "kind/test" # Adding or updating tests |
| 25 | + - "kind/chore" # Maintenance tasks (deps, config, etc.) |
| 26 | + - "kind/ci" # CI/CD changes |
| 27 | + - "kind/performance" # Performance improvements |
| 28 | + - "kind/build" # Build system changes |
| 29 | + - "kind/security" # Security fixes |
| 30 | + - "kind/dependencies" # Dependency updates |
| 31 | + |
| 32 | + |
| 33 | + # Priority labels - Optional: uncomment to require priority classification |
| 34 | + # Common priorities: low, medium, high, critical |
| 35 | + # - "priority/medium" # Uncomment to require priority label |
| 36 | + |
| 37 | + # Area/Component labels - Optional: uncomment to require component classification |
| 38 | + # Common areas: frontend, backend, api, database, infrastructure, tooling |
| 39 | + # - "area/backend" # Uncomment to require area label |
| 40 | + |
| 41 | + # Size labels - Optional: uncomment to require size estimation |
| 42 | + # Common sizes: XS, S, M, L, XL (for effort estimation) |
| 43 | + # - "size/M" # Uncomment to require size label |
0 commit comments