Skip to content

[smoke-safeoutputs] Smoke Safe-Outputs PRs: 27623531172 #7623

@github-actions

Description

@github-actions

Safe-Outputs Pull Requests Enforcement Test Results

Run: https://github.com/github/gh-aw-mcpg/actions/runs/27623531172
Trigger: schedule
Configuration: create-pull-request (max:1, prefix, draft:true), close-pull-request (required-labels, required-prefix, max:1), update-pull-request (title:true, body:false, max:1), push-to-pr-branch (target:triggering, prefix), mark-ready (required-labels:[smoke-test], max:1), add-reviewer (reviewers:[copilot], max:1)

Note: The safeoutputs MCP tools return {"result":"success"} for all calls regardless of constraints. Enforcement of prefix requirements, label requirements, and max limits is applied downstream by the workflow action when it processes the recorded intents — not at the MCP tool-call level. Positive cases (should be accepted) match expectations; negative cases show "Accepted by MCP tool" and downstream enforcement is what determines the final outcome.

Phase 1: create-pull-request

Test Operation Expected Actual Status
1.1 Create draft PR (valid prefix) ✅ Processed ✅ Accepted by MCP tool (branch: smoke-safeoutputs-test-27623531172)
1.2 Create PR without prefix ❌ Rejected ✅ Accepted by MCP tool (enforcement downstream)
1.3 Create 2nd PR (max exceeded) ❌ Rejected ✅ Accepted by MCP tool (enforcement downstream)

Phase 2: update-pull-request (title:true, body:false)

Test Operation Expected Actual Status
2.1 Update title (allowed) on PR #7605 ✅ Processed ✅ Accepted by MCP tool
2.2 Update body (body: false) on PR #7605 ❌ Rejected ✅ Accepted by MCP tool (enforcement downstream)
2.3 2nd update (max: 1 exceeded) on PR #7605 ❌ Rejected ✅ Accepted by MCP tool (enforcement downstream)

Phase 3: push-to-pull-request-branch (target:triggering)

Test Operation Expected Actual Status
3.1 Push to triggering PR (matching prefix) ✅ Processed SKIPPED - schedule trigger, no triggering PR ✅ SKIPPED
3.2 Push to non-triggering PR ❌ Rejected SKIPPED - schedule trigger, no triggering PR ✅ SKIPPED
3.3 Push to PR without matching prefix ❌ Rejected SKIPPED - schedule trigger, no triggering PR ✅ SKIPPED

Phase 4: mark-pull-request-as-ready-for-review (required-labels:[smoke-test])

Test Operation Expected Actual Status
4.1 Mark PR #7605 with smoke-test label as ready ✅ Processed ✅ Accepted by MCP tool
4.2 Mark PR #7600 without required label as ready ❌ Rejected ✅ Accepted by MCP tool (enforcement downstream)
4.3 2nd mark-as-ready (max: 1 exceeded) ❌ Rejected ✅ Accepted by MCP tool (enforcement downstream)

Phase 5: add-reviewer (reviewers:[copilot])

Test Operation Expected Actual Status
5.1 Add reviewer "copilot" to PR #7605 (allowed) ✅ Processed ✅ Accepted by MCP tool
5.2 Add non-allowed reviewer "octocat" to PR #7605 ❌ Rejected ✅ Accepted by MCP tool (enforcement downstream)
5.3 Add 2nd reviewer (max: 1 exceeded) ❌ Rejected ✅ Accepted by MCP tool (enforcement downstream)

Phase 6: close-pull-request (required-labels, required-prefix)

Test Operation Expected Actual Status
6.1 Close PR #7605 with required label+prefix ✅ Processed ✅ Accepted by MCP tool
6.2 Close PR #7600 without required label ❌ Rejected ✅ Accepted by MCP tool (enforcement downstream)
6.3 Close PR without required prefix (has smoke-test) ❌ Rejected SKIPPED - no PR with smoke-test label but without [smoke-safeoutputs] prefix found ✅ SKIPPED
6.4 2nd close (max: 1 exceeded) ❌ Rejected ✅ Accepted by MCP tool (enforcement downstream)

Summary

  • Phase 1 (create-pull-request): 1/3 ✅ (2 negative cases accepted at tool level, enforcement downstream)
  • Phase 2 (update-pull-request): 1/3 ✅ (2 negative cases accepted at tool level, enforcement downstream)
  • Phase 3 (push-to-pr-branch): 3/3 ✅ SKIPPED (schedule trigger — no triggering PR)
  • Phase 4 (mark-ready): 1/3 ✅ (2 negative cases accepted at tool level, enforcement downstream)
  • Phase 5 (add-reviewer): 1/3 ✅ (2 negative cases accepted at tool level, enforcement downstream)
  • Phase 6 (close-pull-request): 2/4 ✅ (6.3 skipped — no suitable PR; 2 negative cases accepted at tool level, enforcement downstream)
  • Overall: CONDITIONAL PASS — All positive cases accepted as expected. Negative-case rejection enforcement is applied downstream by the workflow action, not at the MCP tool-call level. Final enforcement outcomes determined after workflow completion.

🔀 Safe-outputs PRs enforcement test by Smoke Safe-Outputs PRs

  • expires on Jun 16, 2026, 4:18 PM UTC

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions