Remove labeling from agentic issue triage workflow#4289
Merged
priyankatiwari08 merged 1 commit intoMay 19, 2026
Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
Follow-up to #4177 that strips all label-application behavior from the agentic issue-triage workflow. The workflow now only reads the issue and posts a single triage summary comment; labeling is left to GitHub Projects and human triage.
Changes:
- Removes
add-labelsfrom safe-outputs frontmatter and all label-related instructions/template language inissue-triage.md; adds an explicit "do not calladd_labels" guardrail and moves the AI disclaimer above Next Steps. - Drops the "Required Context" step that scanned
.github/**.mdfiles. - Recompiles
issue-triage.lock.ymland updatesactions-lock.jsonaccordingly.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| .github/workflows/issue-triage.md | Removes label actions, required-context step, and updates triage-summary template/next-steps wording. |
| .github/workflows/issue-triage.lock.yml | Recompiled lock; however it appears to be recompiled with an older gh-aw CLI (v0.68.1) which downgrades many unrelated pinned versions and removes recent features. |
| .github/aw/actions-lock.json | Recompiled lock that downgrades the setup action and removes pinned firewall container digests. |
da03892 to
0913036
Compare
0913036 to
0b4705b
Compare
0b4705b to
ab48a9b
Compare
ab48a9b to
5ea2643
Compare
- Remove add-labels safe-output from frontmatter - Remove add_labels action instructions from workflow body - Remove Required Context section (full .github/ scan) - Update triage comment template (area from table, not label) - Move AI disclaimer before Next Steps - Recompile lock.yml Labels will be managed via GitHub Projects and human triage instead.
5ea2643 to
c7f9b77
Compare
cheenamalhotra
approved these changes
May 14, 2026
apoorvdeshmukh
approved these changes
May 19, 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.
Summary
Follow-up to #4177. Removes all label-related functionality from the agentic issue triage workflow per team decision to manage labels via GitHub Projects and human triage instead.
Changes
Frontmatter:
add-labels: max: 5from safe-outputs (workflow can no longer apply labels)Workflow instructions:
add_labelsfrom the task list (now: read → comment only)add_labels. Do NOT apply any labels.".github/markdown files)add_labelsaction block (Triage Needed, Area, Needs More Info, Repro Available, Regression labels)Lock file:
issue-triage.lock.ymlviagh aw compilesafe_outputsjob no longer includes label-related stepsWhat the workflow still does
Prerequisites simplified
With labeling removed, the only prerequisite for this workflow is:
COPILOT_GITHUB_TOKENsecret — required for Copilot inferenceThe
Triage Needed :new:label creation is no longer required.Tested on
Developed on priyankatiwari08/SqlClient-test-prtiwar