Spaces:
Running
Running
Merge pull request #48 from jlowin/ai-labeler
Browse files- .github/ai-labeler.yml +3 -4
.github/ai-labeler.yml
CHANGED
|
@@ -1,6 +1,6 @@
|
|
| 1 |
instructions: |
|
| 2 |
Apply the minimal set of labels that accurately characterize the issue/PR:
|
| 3 |
-
- Use at most 1-2 labels unless there's a compelling reason for more
|
| 4 |
- Prefer specific labels (bug, feature) over generic ones (question, help wanted)
|
| 5 |
- For PRs that fix bugs, use 'bug' not 'enhancement'
|
| 6 |
- Never combine: bug + enhancement, feature + enhancement. For these labels, only choose the most relevant one.
|
|
@@ -12,9 +12,8 @@ labels:
|
|
| 12 |
instructions: |
|
| 13 |
Apply when describing or fixing unexpected behavior:
|
| 14 |
- Issues: Clear error messages or unexpected outcomes
|
| 15 |
-
- PRs:
|
| 16 |
-
Don't apply
|
| 17 |
-
beyond fixing the bug
|
| 18 |
|
| 19 |
- documentation:
|
| 20 |
description: "Improvements or additions to documentation"
|
|
|
|
| 1 |
instructions: |
|
| 2 |
Apply the minimal set of labels that accurately characterize the issue/PR:
|
| 3 |
+
- Use at most 1-2 labels unless there's a compelling reason for more. It's ok to use no labels.
|
| 4 |
- Prefer specific labels (bug, feature) over generic ones (question, help wanted)
|
| 5 |
- For PRs that fix bugs, use 'bug' not 'enhancement'
|
| 6 |
- Never combine: bug + enhancement, feature + enhancement. For these labels, only choose the most relevant one.
|
|
|
|
| 12 |
instructions: |
|
| 13 |
Apply when describing or fixing unexpected behavior:
|
| 14 |
- Issues: Clear error messages or unexpected outcomes
|
| 15 |
+
- PRs: Standalone fixes for broken functionality or closing bug reports.
|
| 16 |
+
Don't apply bug unless the issue or PR is predominantly about a specific bug.
|
|
|
|
| 17 |
|
| 18 |
- documentation:
|
| 19 |
description: "Improvements or additions to documentation"
|