docs: note that non-default labels must exist before running the triage workflow - #52376
Merged
Merged
Conversation
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Document label pre-creation requirement in AI issue triage guide
docs: note that non-default labels must exist before running the triage workflow
Aug 12, 2026
Contributor
PR Triage SummaryTotal score: 18/100 Automated triage — see labels applied for classification. Full report in the triage issue.
|
pelikhan
approved these changes
Aug 13, 2026
Contributor
There was a problem hiding this comment.
Pull request overview
Documents the label pre-creation requirement for the AI issue triage workflow.
Changes:
- Explains that allowed labels must exist before execution.
- Provides CLI and UI creation options.
Show a summary per file
| File | Description |
|---|---|
docs/src/content/docs/guides/ai-issue-triage.md |
Adds label setup guidance. |
Review details
💡 Add a code-review agent skill for context-aware, tailored reviews. Learn more in the docs.
- Files reviewed: 1/1 changed files
- Comments generated: 1
- Review effort level: Balanced
|
|
||
| `add-labels` and `add-comment` matter for security because the agent does not receive direct write access to issues. gh-aw validates label names and comment output before posting, which reduces the risk of prompt injection turning repository analysis into unrestricted writes. | ||
|
|
||
| Every label listed under `allowed` must already exist in the target repository. `bug`, `feature`, and `question` ship as GitHub defaults, but labels such as `needs-info`, `priority/p0`, `priority/p1`, and `priority/p2` do not, and applying a missing label fails at runtime. Create them before the first run with `gh label create needs-info` (repeat per label) or from the repository's Settings > Labels page. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The AI issue triage guide lists
needs-infoandpriority/p0–p2inadd-labels.allowed, but those are not GitHub default labels. Copying the example into a fresh repo produces an opaque runtime failure (label API 404) with nothing in the guide to explain it.Changes
docs/src/content/docs/guides/ai-issue-triage.md: added one paragraph after the security-rationale section stating that every label inallowedmust already exist, calling out which ones in the example are non-default, and pointing atgh label create/ Settings > Labels as the fix.Documentation-only; no workflow or code changes.