Skip to content

Remove labeling from agentic issue triage workflow#4289

Merged
priyankatiwari08 merged 1 commit into
dotnet:mainfrom
priyankatiwari08:feature/agentic-issue-triage-removelabel
May 19, 2026
Merged

Remove labeling from agentic issue triage workflow#4289
priyankatiwari08 merged 1 commit into
dotnet:mainfrom
priyankatiwari08:feature/agentic-issue-triage-removelabel

Conversation

@priyankatiwari08
Copy link
Copy Markdown
Contributor

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:

  • Removed add-labels: max: 5 from safe-outputs (workflow can no longer apply labels)

Workflow instructions:

  • Removed add_labels from the task list (now: read → comment only)
  • Added explicit instruction: "Do NOT call add_labels. Do NOT apply any labels."
  • Removed "Required Context" section (no longer scans all .github/ markdown files)
  • Removed entire add_labels action block (Triage Needed, Area, Needs More Info, Repro Available, Regression labels)
  • Updated triage summary template: Area field now says "Best matching area from classification table" instead of "Area label applied"
  • Moved AI disclaimer note before Next Steps guidance
  • Refined Next Steps to be maintainer-focused guidance

Lock file:

  • Recompiled issue-triage.lock.yml via gh aw compile
  • safe_outputs job no longer includes label-related steps

What the workflow still does

  1. Reads the new issue via GitHub MCP (read-only)
  2. Classifies: issue type, area, environment completeness, duplicates, regression
  3. Posts one triage summary comment with structured analysis table

Prerequisites simplified

With labeling removed, the only prerequisite for this workflow is:

  1. COPILOT_GITHUB_TOKEN secret — required for Copilot inference

The Triage Needed :new: label creation is no longer required.

Tested on

Developed on priyankatiwari08/SqlClient-test-prtiwar

@priyankatiwari08 priyankatiwari08 requested a review from a team as a code owner May 14, 2026 10:37
Copilot AI review requested due to automatic review settings May 14, 2026 10:37
@github-project-automation github-project-automation Bot moved this to To triage in SqlClient Board May 14, 2026
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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-labels from safe-outputs frontmatter and all label-related instructions/template language in issue-triage.md; adds an explicit "do not call add_labels" guardrail and moves the AI disclaimer above Next Steps.
  • Drops the "Required Context" step that scanned .github/**.md files.
  • Recompiles issue-triage.lock.yml and updates actions-lock.json accordingly.

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.

Comment thread .github/workflows/issue-triage.lock.yml Outdated
Comment thread .github/aw/actions-lock.json
@priyankatiwari08 priyankatiwari08 force-pushed the feature/agentic-issue-triage-removelabel branch from da03892 to 0913036 Compare May 14, 2026 10:44
Copilot AI review requested due to automatic review settings May 14, 2026 10:47
@priyankatiwari08 priyankatiwari08 force-pushed the feature/agentic-issue-triage-removelabel branch from 0913036 to 0b4705b Compare May 14, 2026 10:47
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated no new comments.

@priyankatiwari08 priyankatiwari08 force-pushed the feature/agentic-issue-triage-removelabel branch from 0b4705b to ab48a9b Compare May 14, 2026 10:52
Copilot AI review requested due to automatic review settings May 14, 2026 11:04
@priyankatiwari08 priyankatiwari08 force-pushed the feature/agentic-issue-triage-removelabel branch from ab48a9b to 5ea2643 Compare May 14, 2026 11:04
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated no new comments.

- 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.
@priyankatiwari08 priyankatiwari08 force-pushed the feature/agentic-issue-triage-removelabel branch from 5ea2643 to c7f9b77 Compare May 14, 2026 11:06
@priyankatiwari08 priyankatiwari08 added this to the 7.1.0-preview2 milestone May 14, 2026
@cheenamalhotra cheenamalhotra self-assigned this May 14, 2026
@priyankatiwari08 priyankatiwari08 merged commit c92d901 into dotnet:main May 19, 2026
6 of 7 checks passed
@github-project-automation github-project-automation Bot moved this from To triage to Done in SqlClient Board May 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

4 participants