Skip to content

android-reviewer: @copilot prefix for Copilot-authored PRs#10930

Merged
jonathanpeppers merged 1 commit intomainfrom
android-reviewer-copilot-prefix
Mar 13, 2026
Merged

android-reviewer: @copilot prefix for Copilot-authored PRs#10930
jonathanpeppers merged 1 commit intomainfrom
android-reviewer-copilot-prefix

Conversation

@simonrozsival
Copy link
Member

@simonrozsival simonrozsival commented Mar 13, 2026

When the android-reviewer skill reviews a PR authored by Copilot and the verdict is ⚠️ Needs Changes or ❌ Reject, the review body is now prefixed with @copilot so the comment automatically triggers the Copilot coding agent to address the feedback.

No prefix is added for ✅ LGTM verdicts.

Used here: #10920 (review)

When the PR author is Copilot and the review verdict is Needs Changes or
Reject, prefix the review body with @copilot so the comment automatically
triggers Copilot to address the feedback.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot AI review requested due to automatic review settings March 13, 2026 07:41
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

Updates the android-reviewer skill guidance so that reviews on Copilot-authored PRs can automatically trigger the Copilot coding agent to address feedback when the verdict is not LGTM.

Changes:

  • Add an instruction to prefix the review JSON body with @copilot when the PR author is Copilot and the verdict is ⚠️ Needs Changes or ❌ Reject.
  • Explicitly exclude ✅ LGTM verdicts from receiving the @copilot prefix.

@jonathanpeppers jonathanpeppers merged commit 23594e9 into main Mar 13, 2026
9 checks passed
@jonathanpeppers jonathanpeppers deleted the android-reviewer-copilot-prefix branch March 13, 2026 13:14
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.

3 participants