Skip to content

[EngSys] Agentic Triage Workflow#49653

Open
jsquire wants to merge 4 commits into
Azure:mainfrom
jsquire:eng/triage
Open

[EngSys] Agentic Triage Workflow#49653
jsquire wants to merge 4 commits into
Azure:mainfrom
jsquire:eng/triage

Conversation

@jsquire

@jsquire jsquire commented Jun 26, 2026

Copy link
Copy Markdown
Member

Summary

The focus of these changes is to move from the legacy JimBot issue triage to an agentic workflow version. This improves accuracy of labeling and adds support for identifying bot-sourced issues and issues for deprecated packages.

The focus of these changes is to move from the
legacy JimBot issue triage to an agentic workflow
version.  This improves accuracy of labeling and
adds support for identifying bot-sourced issues and
issues for deprecated packages.
@jsquire jsquire added this to the 2026-07 milestone Jun 26, 2026
@jsquire jsquire self-assigned this Jun 26, 2026
Copilot AI review requested due to automatic review settings June 26, 2026 23:57
@jsquire jsquire requested review from a team as code owners June 26, 2026 23:57
@jsquire jsquire added EngSys This issue is impacting the engineering system. Client This issue points to a problem in the data-plane of the library. labels Jun 26, 2026

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Pull request overview

This PR replaces the legacy JimBot-style initial issue triage with a GitHub Agentic Workflows (gh-aw) based triage workflow, adding the new issue triage prompt + compiled lock workflow, and updating repo wiring/docs to support author classification, label prediction, CODEOWNERS-based routing, and deprecated-package detection.

Changes:

  • Added a new agentic issue triage workflow definition (issue-triage.md) and its compiled GitHub Actions workflow (issue-triage.lock.yml).
  • Added agent/skill documentation and repo MCP configuration to support creating/debugging/upgrading gh-aw workflows.
  • Disabled the legacy InitialIssueTriage path in the event processor configuration and marked lock files as generated/merge-ours.

Reviewed changes

Copilot reviewed 8 out of 9 changed files in this pull request and generated 7 comments.

Show a summary per file
File Description
.github/workflows/issue-triage.md Source workflow prompt and safe-outputs configuration for agentic issue triage and routing.
.github/workflows/issue-triage.lock.yml Generated compiled workflow consumed by GitHub Actions.
.github/skills/agentic-workflows/SKILL.md Router skill for gh-aw workflow design/create/debug/upgrade requests.
.github/skills/agentic-workflow-designer/SKILL.md Interview-style workflow designer skill scaffolding for gh-aw workflows.
.github/mcp.json Adds repo MCP server configuration for gh aw mcp-server tools.
.github/event-processor.config Disables legacy initial issue triage in the event processor.
.github/aw/actions-lock.json Adds action pin entry for gh-aw setup action.
.github/agents/agentic-workflows.md Adds a dispatcher agent doc for working with gh-aw in this repo.
.gitattributes Marks *.lock.yml as generated and sets merge strategy to ours.

Comment thread .github/workflows/issue-triage.md
Comment thread .github/workflows/issue-triage.md
Comment thread .github/workflows/issue-triage.md Outdated
Comment thread .github/workflows/issue-triage.md Outdated
Comment thread .github/workflows/issue-triage.md Outdated
Comment thread .github/skills/agentic-workflows/SKILL.md Outdated
Comment thread .github/agents/agentic-workflows.md
jsquire and others added 2 commits June 26, 2026 17:12
actionlint v1.7.12 (latest release) does not recognize the newer GitHub
Actions features emitted in the generated gh-aw lock files: the
'copilot-requests' permission scope and the 'queue' key under 'concurrency'.
Add path-scoped ignores in .github/actionlint.yaml for *.lock.yml only, so
hand-authored workflows remain fully linted.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

@vcolin7 vcolin7 left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Added some initial comments

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

I don't think we need to include this file if we're referencing it from the gh-aw repository.

Comment thread .vscode/cspell.json
"*.certificate",
"*.crt",
"*.yml",
".github/skills/agentic-workflow-designer/*",

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

If we end up removing the designer skill from the repo in favor of referencing it, we should also remove this line.

Comment thread .github/mcp.json

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

I didn't see a file like this on the .NET repo. Is there a particular reason we don't have one over there?

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

There's an mcp.json file under /.vscode, but it references other MCP servers.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

That's a good catch. The infrastructure set this up. My best guess is that the gh aw init output changed since we did .NET and this is new. Poking copilot on it to see if we should reflect this over in .NET as well or remove it here.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

This file's counterpart on the .NET repo pins other versions. Should we also pin some of those here?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

The .NET version got updated today as well. Both .NET and Java should be using the latest version of the updates.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Client This issue points to a problem in the data-plane of the library. EngSys This issue is impacting the engineering system.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants