zoriya/v10
1
0
Fork 0
mirror of https://github.com/zoriya/v10.git synced 2026-08-16 02:45:09 +00:00
Code Issues Packages Projects Releases Wiki Activity

chore(ci): scope triage label to external authors (#1550)

Browse Source
This commit is contained in:
Darius Cepulis
2026-05-18 13:06:59 -07:00
committed by GitHub
parent 7035407963
commit e68ace82ff
2 changed files with 18 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.github/workflows/issue-triage.yml
+5 -4
View File
@@ -60,17 +60,18 @@ jobs:
- Review labels used on related/cross-referenced issues before deciding.
- Add missing useful labels and remove clearly incorrect labels.
- Do not create new labels; only use existing labels.
- Never apply these labels — they are managed manually:
- Never apply these labels — they are managed manually or by other automation:
- `epic` (epic linkage is curated by maintainers)
- Priority labels (`P0`, `P1`, `P2`)
- `triage` (applied by automation only for external authors)
Surface these as recommendations in step 8 instead.
3. Detect probable duplicates:
- Search for existing issues with the same bug/request symptoms, stack traces, repro steps, or scope.
- If a likely duplicate is found, leave one concise comment linking the likely canonical issue and why it appears duplicated.
- If confidence is not high, do not mark as duplicate; instead add `triage` label for human review.
- If confidence is not high, do not mark as duplicate; instead leave a concise comment flagging the uncertainty for human review.
- Do not auto-close duplicates unless there is very high confidence and no meaningful unique information.
4. Escalate uncertainty:
- Add `triage` label when classification is ambiguous, conflicting, or needs human judgment.
- When classification is ambiguous, conflicting, or needs human judgment, leave a concise comment flagging the uncertainty rather than applying labels.
5. Suggest docs/resources when helpful:
- Use https://videojs.org/llms.txt as the primary source to discover relevant docs links.
- If likely already documented, suggest 1-3 relevant docs links with a short reason.
@@ -81,7 +82,7 @@ jobs:
- If the issue suggests the user is struggling to achieve something with the library, provide practical guidance.
- Suggest the most relevant documented approach with 1-3 links (from https://videojs.org/llms.txt discovery).
- Include concise next steps or a minimal example/snippet when it materially helps.
- If docs appear incomplete or unclear, call that out and add `triage` for human follow-up.
- If docs appear incomplete or unclear, call that out in a comment for human follow-up.
8. Planning recommendations (comment-only):
- Review roadmap context at https://github.com/orgs/videojs/projects/7 and current repository milestones.
- Identify likely related epics/issues and related open PRs.