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
Test 1.2 FAIL: create_discussion max:1 enforcement did not reject a second call — tool returned {"result":"success"} for both the first and second discussion creation attempts. Note: discussion from Test 1.1 was not immediately visible in GitHub's list API (totalCount unchanged at 171), suggesting safe-outputs may execute creates asynchronously after the agent session ends; max enforcement may be deferred or not enforced at declaration time.
Test 3.3 FAIL: close_discussion max:1 enforcement did not reject a second close call — both Test 3.1 and 3.3 returned {"result":"success"}. Enforcement of max for close-discussion appears not working.
Test 3.2 SKIPPED: All visible discussions in the repo use the "smoke-test" label (all created by prior smoke test runs). No suitable unlabeled discussion found to test required-label rejection.
Phase 2 note: Update tests (2.1, 2.2) were run against discussion [smoke-safeoutputs] Enforcement Test 28029473878 #7978 (previous run's discussion) since the discussion created in Test 1.1 was not immediately visible in the GitHub API.
Safe-Outputs Discussions Enforcement Test Results
Run: https://github.com/github/gh-aw-mcpg/actions/runs/28068411113
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"}— Processed{"result":"success"}— Processed (not rejected)Phase 2: update-discussion
{"result":"success"}— Processed{"result":"success"}— ProcessedPhase 3: close-discussion
{"result":"success"}— Processed{"result":"success"}— Processed (not rejected)Phase 4: add-comment (target: triggering)
Summary
Notes
create_discussionmax:1 enforcement did not reject a second call — tool returned{"result":"success"}for both the first and second discussion creation attempts. Note: discussion from Test 1.1 was not immediately visible in GitHub's list API (totalCount unchanged at 171), suggesting safe-outputs may execute creates asynchronously after the agent session ends; max enforcement may be deferred or not enforced at declaration time.close_discussionmax:1 enforcement did not reject a second close call — both Test 3.1 and 3.3 returned{"result":"success"}. Enforcement of max for close-discussion appears not working.