skills(forge-issue-filing): soften labels section per review
This commit is contained in:
parent
ef40b03c87
commit
5300c242f3
1 changed files with 7 additions and 4 deletions
|
|
@ -84,10 +84,13 @@ hive-forge repo-labels
|
||||||
```
|
```
|
||||||
|
|
||||||
Attach whatever scope labels the repo actually uses (commonly a `type/*`
|
Attach whatever scope labels the repo actually uses (commonly a `type/*`
|
||||||
and an `area/*`, but check - taxonomies differ per repo). Skipping labels
|
and an `area/*`, but check - taxonomies differ per repo) when you
|
||||||
entirely is worse than a slightly-off guess: an unlabeled issue is what
|
already know them - it saves a round trip. But don't stress over an
|
||||||
`hive-forge lint unlabeled --scope <scope>` exists to catch, so an
|
unlabeled issue: labeling what's already filed is what triage coverage
|
||||||
unlabeled issue you filed becomes someone else's triage cleanup.
|
(`hive-forge lint unlabeled --scope <scope>`, and whatever agent/process
|
||||||
|
this hive runs to sweep it) exists for. Guessing at a label you're not
|
||||||
|
sure of just to avoid leaving it blank can do more harm than leaving it
|
||||||
|
for triage to get right.
|
||||||
|
|
||||||
## 5. Assignee: leave it to triage unless you know who owns it
|
## 5. Assignee: leave it to triage unless you know who owns it
|
||||||
|
|
||||||
|
|
|
||||||
Loading…
Reference in a new issue