Skip to content

feat: post issue comment when reviewer approves a plan#4

Open
Maxtanh-Meta wants to merge 1 commit into
logosc:mainfrom
Maxtanh-Meta:reviewer-approval-comment
Open

feat: post issue comment when reviewer approves a plan#4
Maxtanh-Meta wants to merge 1 commit into
logosc:mainfrom
Maxtanh-Meta:reviewer-approval-comment

Conversation

@Maxtanh-Meta

Copy link
Copy Markdown

Summary

Post an issue comment when the reviewer agent approves a plan, matching the existing behavior on rejection.

Before: Only rejections posted a comment ([symphony-go] reviewer rejected the plan: ...). Approvals were only logged.

After: Approvals also post a comment ([symphony-go] ✅ reviewer approved the plan: ...), giving operators and issue authors visibility into the review decision without needing log access.

Changes

  • internal/orchestrator/job.go: Add 3 lines to post approval reasons as an issue comment before proceeding to implementation.

Testing

Tested end-to-end with a live repo — reviewer approval comment appears on the GitHub issue before implementation begins.

Previously, the reviewer only posted a comment on rejection. This makes
the approval path equally visible — operators and issue authors can see
why the reviewer approved and that the gate was evaluated, without
needing to check orchestrator logs.
@Maxtanh-Meta

Copy link
Copy Markdown
Author
Screenshot 2026-05-14 at 12 13 40 PM

@Maxtanh-Meta

Copy link
Copy Markdown
Author

Code Review (via Codex)

Overall: ✅ Approve

The change adds a best-effort GitHub comment on reviewer approval, matching the existing pattern for rejections. Codex found no correctness issues.

  • Follows the same _, _ = o.deps.GitHub.PostIssueComment(...) fire-and-forget pattern used elsewhere
  • 3-line addition, well-scoped
  • No new test failures introduced (only pre-existing TestPerAxisWorkflowAndValidation fails, unrelated)

Ship it.

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.

1 participant