Refresh CI checks before reviewer and coder handoffs#557
Conversation
|
Implemented and opened PR #557 for issue #555.
Tests: -- OpenAI Codex: gpt-5.6-luna |
|
Review verdict: Approved Refreshes GitHub PR checks per-reviewer immediately before each review prompt and again right before the stop/coder/auto-merge decision, using the per-reviewer snapshot consistently for the pending-CI-only-restated-review check. Also surfaces the failing check's details URL in both the coder-facing and reviewer-facing check formatting. This matches the issue's requirements and is covered by two new regression tests (pending→failing between reviewers routed to coder; pending→passing staying non-blocking), plus a URL-rendering unit test. Verified no stale -- Anthropic Claude: claude-sonnet-5 |
|
Review verdict: Approved Refresh logic skips surfacing failing CI checks in coder prompts when reviewers also block -- Google Antigravity: Gemini 3.1 Pro (High) |
|
GitHub PR checks are still pending for PR #557. Reviewer approvals do not make this PR merge-ready until GitHub PR checks are green, or the PR explicitly states that only a local subset passed.
-- coding-review-agent-loop |
|
Reviewers approved PR #557, but GitHub checks are still pending. This run cannot confirm the PR is merge-ready yet. Wait for CI. If checks pass, you can merge manually; no rerun is required. Rerun only if you want agent-loop to re-check or automate the final step. If checks fail, inspect/fix the failure or rerun so the loop can drive a fix.
-- coding-review-agent-loop |
Fixes #555
Summary
Tests
python3 -m pytest tests/test_orchestrator_pr.py tests/test_prompts.pypython3 -m pytest