Safe-Outputs Reviews Enforcement Test Results
Run: https://github.com/github/gh-aw-mcpg/actions/runs/33285084161
Trigger: schedule
Configuration: create-pr-review-comment (max:2, target:triggering), submit-pr-review (max:1, footer:if-body), reply-to-review-comment (max:2), resolve-review-thread (max:2)
Phase 1: create-pull-request-review-comment (max:2, target:triggering)
| Test |
Operation |
Expected |
Actual |
Status |
| 1.1 |
Create 1st review comment (triggering PR) |
✅ Processed |
No triggering PR (schedule trigger) |
SKIPPED |
| 1.2 |
Create 2nd review comment (triggering PR) |
✅ Processed |
No triggering PR (schedule trigger) |
SKIPPED |
| 1.3 |
Create 3rd review comment (max exceeded) |
❌ Rejected |
No triggering PR (schedule trigger) |
SKIPPED |
| 1.4 |
Create comment on non-triggering PR |
❌ Rejected |
No triggering PR (schedule trigger) |
SKIPPED |
Phase 2: submit-pull-request-review (max:1, footer:if-body)
| Test |
Operation |
Expected |
Actual |
Status |
| 2.1 |
Submit review with body (footer added) |
✅ Processed |
No triggering PR (schedule trigger) |
SKIPPED |
| 2.2 |
footer: "if-body" behavior verified |
CONFIG NOTED |
Not verified — Test 2.1 skipped |
SKIPPED |
| 2.3 |
Submit 2nd review (max exceeded) |
❌ Rejected |
No triggering PR (schedule trigger) |
SKIPPED |
Phase 3: reply-to-pull-request-review-comment (max:2)
| Test |
Operation |
Expected |
Actual |
Status |
| 3.1 |
Reply to 1st review comment |
✅ Processed |
No review comments created (Phase 1 skipped) |
SKIPPED |
| 3.2 |
Reply to 2nd review comment |
✅ Processed |
No review comments created (Phase 1 skipped) |
SKIPPED |
| 3.3 |
3rd reply (max exceeded) |
❌ Rejected |
No review comments created (Phase 1 skipped) |
SKIPPED |
Phase 4: resolve-pull-request-review-thread (max:2)
| Test |
Operation |
Expected |
Actual |
Status |
| 4.1 |
Resolve 1st review thread |
✅ Processed |
No review threads available (Phase 1 skipped) |
SKIPPED |
| 4.2 |
Resolve 2nd review thread |
✅ Processed |
No review threads available (Phase 1 skipped) |
SKIPPED |
| 4.3 |
Resolve 3rd thread (max exceeded) |
❌ Rejected |
No review threads available (Phase 1 skipped) |
SKIPPED |
Summary
- Phase 1 (review-comment): 0/4 — SKIPPED
- Phase 2 (submit-review): 0/3 — SKIPPED
- Phase 3 (reply-to-comment): 0/3 — SKIPPED
- Phase 4 (resolve-thread): 0/3 — SKIPPED
- Overall: PARTIAL (schedule run)
Note: This workflow run was triggered by schedule, so no triggering pull request context was available (pull-request-number: #false in GitHub context). Several open PRs exist in the repo (e.g. #12132, #12130, #12129, #12110, #12105), but per the test matrix, Phases 1–4 all explicitly require the triggering PR context to exercise these safe-output review operations meaningfully (review comments, replies, and thread resolution build on artifacts from earlier phases in the same run). No standalone open PR was substituted since the task instructions scope these to the triggering PR only. Full validation of Phases 1–4 requires re-running this workflow with a pull_request trigger event (ideally labeled smoke-safeoutputs).
[Note: Most tests require pull_request trigger with "smoke-safeoutputs" label to fully execute]
🔍 Safe-outputs reviews enforcement test by Smoke Safe-Outputs Reviews
Safe-Outputs Reviews Enforcement Test Results
Run: https://github.com/github/gh-aw-mcpg/actions/runs/33285084161
Trigger: schedule
Configuration: create-pr-review-comment (max:2, target:triggering), submit-pr-review (max:1, footer:if-body), reply-to-review-comment (max:2), resolve-review-thread (max:2)
Phase 1: create-pull-request-review-comment (max:2, target:triggering)
Phase 2: submit-pull-request-review (max:1, footer:if-body)
Phase 3: reply-to-pull-request-review-comment (max:2)
Phase 4: resolve-pull-request-review-thread (max:2)
Summary
Note: This workflow run was triggered by
schedule, so no triggering pull request context was available (pull-request-number: #falsein GitHub context). Several open PRs exist in the repo (e.g. #12132, #12130, #12129, #12110, #12105), but per the test matrix, Phases 1–4 all explicitly require the triggering PR context to exercise these safe-output review operations meaningfully (review comments, replies, and thread resolution build on artifacts from earlier phases in the same run). No standalone open PR was substituted since the task instructions scope these to the triggering PR only. Full validation of Phases 1–4 requires re-running this workflow with apull_requesttrigger event (ideally labeledsmoke-safeoutputs).[Note: Most tests require pull_request trigger with "smoke-safeoutputs" label to fully execute]