Remove non-existent priority labels from issue triage workflow#171
Draft
Remove non-existent priority labels from issue triage workflow#171
Conversation
Remove references to priority/critical, priority/high, priority/medium, and priority/low labels that don't exist in the repository. Update both the source .md file and the compiled .lock.yml to only reference labels that actually exist. The primary workflow failure (COPILOT_GITHUB_TOKEN secret not configured) requires repository administrator action to resolve. Agent-Logs-Url: https://github.com/Azure/AppConfiguration-KubernetesProvider/sessions/b5329499-a2d0-4a60-8dcc-93725d34bb54 Co-authored-by: RichardChen820 <99175581+RichardChen820@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Fix Issue Triage Workflow secret verification failure
Remove non-existent priority labels from issue triage workflow
Apr 7, 2026
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 Issue Triage Workflow (run 23943097631) fails at the "Validate COPILOT_GITHUB_TOKEN secret" step — that requires a repo admin to configure the secret per gh-aw docs. Separately, the workflow references four
priority/*labels that don't exist in the repository, which would cause runtime failures even once the secret is configured.Changes
issue-triage.md: Removepriority/critical,priority/high,priority/medium,priority/lowfrom allowed labels; remove "Assess Priority" prompt section; renumber stepsissue-triage.lock.yml: Update all five locations referencing priority labels (safe-outputs config JSON,add_labelstool description, handler config, workflow description comment/env var)Remaining: repo admin action needed
The
COPILOT_GITHUB_TOKENsecret must be added to the repository settings for the workflow to pass the secret validation step. No code change can address this.