You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Phase 1 (create-discussion): 1/2 ✅ (Test 1.2: max enforcement not triggered — second create returned success)
Phase 2 (update-discussion): 2/2 ✅
Phase 3 (close-discussion): 1/3 ✅ (Test 3.3: max enforcement not triggered — second close returned success; Test 3.2 skipped)
Phase 4 (add-comment): SKIPPED (schedule trigger, no triggering item)
Overall: FAIL
Notes on failures:
Test 1.2: After creating the first discussion (Test 1.1), a second create_discussion call with max:1 was expected to be rejected, but returned {"result":"success"}. The enforcement did not block the second creation.
Test 3.3: After closing the first discussion (Test 3.1), a second close_discussion call with max:1 was expected to be rejected, but returned {"result":"success"}. The enforcement did not block the second close.
Note: The newly created discussion from Test 1.1 did not appear in the GitHub discussions listing during this run (possibly asynchronous creation). Tests 2.1, 2.2, and 3.1 were run against discussion [smoke-safeoutputs] Enforcement Test 26684229707 #6740 (from previous run 26684229707) which was the most recently available discussion with matching properties.
Safe-Outputs Discussions Enforcement Test Results
Run: https://github.com/github/gh-aw-mcpg/actions/runs/26699974315
Trigger: schedule
Configuration tested: create-discussion (max:1, prefix, category), update-discussion (enabled, all fields), close-discussion (required-category:General, required-labels:[smoke-test]), add-comment (max:2, target:triggering)
Phase 1: create-discussion
{"result":"success"}){"result":"success"})Phase 2: update-discussion
{"result":"success"}){"result":"success"})Phase 3: close-discussion
{"result":"success"}){"result":"success"})Phase 4: add-comment (target: triggering)
Summary
Notes on failures:
create_discussioncall withmax:1was expected to be rejected, but returned{"result":"success"}. The enforcement did not block the second creation.close_discussioncall withmax:1was expected to be rejected, but returned{"result":"success"}. The enforcement did not block the second close.