Skip to content

Add resolve:qa bot rule for automated question closure#3071

Closed
lramosvea wants to merge 1 commit intomainfrom
feature/resolve-qa-bot-rule
Closed

Add resolve:qa bot rule for automated question closure#3071
lramosvea wants to merge 1 commit intomainfrom
feature/resolve-qa-bot-rule

Conversation

@lramosvea
Copy link
Contributor

@lramosvea lramosvea commented Mar 4, 2026

Summary

Adds a GitOps resource management rule that watches for the resolve:qa label on issues. When this label is applied (by the Graph SDK Issue Triage Agent), the bot will:

  1. Post a comment redirecting the user to Microsoft Q&A
  2. Close the issue automatically

How it works

User asks triage agent -> Agent classifies issue as question -> User approves -> Agent adds resolve:qa label -> Bot closes with redirect message

This is part of the Graph SDK Issue Intelligence FHL project to help manage the issue backlog across SDK repos.

Changes

  • .github/policies/resourceManagement.yml: Added eventResponderTask that triggers on the resolve:qa label
Microsoft Reviewers: Open in CodeFlow

When the triage agent labels an issue with 'resolve:qa', the bot
will post a message redirecting the user to Microsoft Q&A and
close the issue automatically.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@lramosvea lramosvea requested a review from a team as a code owner March 4, 2026 03:12
Copilot AI review requested due to automatic review settings March 4, 2026 03:12
Copy link
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

Adds a GitOps Resource Management event responder rule to automatically close issues marked as questions by applying the resolve:qa label, posting a redirect comment to Microsoft Q&A.

Changes:

  • Added an eventResponderTask that triggers on Issues Labeled events when the resolve:qa label is present.
  • Posts a Microsoft Q&A redirect message and closes the issue.

@lramosvea lramosvea closed this Mar 4, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants