Skip to content

Improve review aw#13510

Merged
JanKrivanek merged 5 commits into
dotnet:mainfrom
JanKrivanek:dev/jankrivanek/improve-review-aw-trigger
Apr 9, 2026
Merged

Improve review aw#13510
JanKrivanek merged 5 commits into
dotnet:mainfrom
JanKrivanek:dev/jankrivanek/improve-review-aw-trigger

Conversation

@JanKrivanek

@JanKrivanek JanKrivanek commented Apr 9, 2026

Copy link
Copy Markdown
Member

Context

followup of #13503

Improvements:

  • let the workflow autotrigger even for fork PRs - from the users with >= contributor permissions to the repo
  • allow posting code inlined comments as well
  • guide the agent to use the gh-aw dedicated tools if available

Note:

Add create-pull-request-review-comment and submit-pull-request-review
safe-outputs so the reviewer agent posts findings as inline diff comments
(tied to specific file+line) rather than general PR comments. Update
expert-reviewer Wave 3/4 instructions to use the correct tools.

Also adds forks and roles support from previous commit.
@JanKrivanek JanKrivanek requested a review from a team as a code owner April 9, 2026 05:48
Copilot AI review requested due to automatic review settings April 9, 2026 05:48

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

Follow-up to the initial “expert review” workflow integration, expanding it to (1) auto-trigger in more PR scenarios (incl. forks gated by repo roles) and (2) let the reviewer agent post proper inline PR review comments + a final review verdict via gh-aw safe-output tools.

Changes:

  • Add role-gating (admin, maintainer, write) to the slash-command and on-open workflows, and allow fork PRs for the on-open trigger.
  • Extend safe-output tooling to support inline PR review comments and submitting a final PR review (verdict).
  • Update the expert-reviewer agent instructions to prefer gh-aw safe-output tools when available.
Show a summary per file
File Description
.github/workflows/shared/review-shared.md Expands safe-outputs and updates workflow prompt guidance to use inline review comments + final review submission.
.github/workflows/review.agent.md Adds role gating for /review slash-command workflow.
.github/workflows/review.agent.lock.yml Regenerates compiled workflow to include new safe-output tools + role gating wiring.
.github/workflows/review-on-open.agent.md Allows fork PRs and adds explicit role gating for auto-run on PR open/ready.
.github/workflows/review-on-open.agent.lock.yml Regenerates compiled workflow to reflect fork allowance + new safe-output tools + role gating.
.github/agents/expert-reviewer.md Updates posting guidance to use gh-aw safe-output tools and adds a “tool availability” note.

Copilot's findings

  • Files reviewed: 6/6 changed files
  • Comments generated: 2

Comment thread .github/workflows/review-on-open.agent.md Outdated
Comment thread .github/agents/expert-reviewer.md
@JanKrivanek JanKrivanek marked this pull request as draft April 9, 2026 05:54
pull_request from forks does not have access to repo secrets, causing
the activation job to fail at COPILOT_GITHUB_TOKEN validation.

Switch to pull_request_target which runs in the base repo context with
full secret access. This is safe because:
- The agent reads diffs via GitHub MCP tools, not by executing PR code
- roles: [admin, maintainer, write] restricts to trusted contributors
- Checkout is only for .github and .agents folders from the base branch

Also drops ready_for_review type (not supported by gh-aw compiler for
pull_request_target). Draft-to-ready PRs can use /review command.

Addresses Copilot review comment about misleading roles comment.
@JanKrivanek JanKrivanek marked this pull request as ready for review April 9, 2026 07:41
@JanKrivanek JanKrivanek closed this Apr 9, 2026
@JanKrivanek JanKrivanek reopened this Apr 9, 2026
@JanKrivanek JanKrivanek enabled auto-merge April 9, 2026 07:41
@JanKrivanek JanKrivanek merged commit 3f8df22 into dotnet:main Apr 9, 2026
10 checks passed
This was referenced Jun 11, 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.

3 participants