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
{{ message }}
Repository navigation
No built-in safe output for creating or editing wiki pages #28608
Status (2026-10-07; Maintainer direction): In the October 7 discussion, a maintainer requested safe-outputs.edit-wiki-page, with creation and updates implied. The next step is to specify and implement that built-in safe output; the request does not establish that it has shipped.
Current-state refresher (2026-10-16): still relevant. Checked default-branch snapshot 0d15bd1, not just the issue's open status.
Wiki checkout support exists in the checkout generator, but this is not a privileged create/update wiki safe output. The current safe-output configuration does not provide edit-wiki-page. The related implementations in #29626 and #1080 are closed without merging; their descriptions should not be read as shipped support.
The outstanding work remains the built-in create/update safe output requested in the October 7 maintainer comment, including its trusted write path and policy validation. This is a source/history assessment; no workflow execution was attempted.
2026-10-22 assessment: still relevant; no built-in safe-outputs.edit-wiki-page.
The current SafeOutputsConfig still has no wiki create/update output. The implementations #29626 and #1080 remain closed unmerged.
There are related shipped capabilities, but they are not this API: #28900 added wiki checkout; #19800 added wiki-backed repo-memory; #36818 corrected its changed-file limit. Checkout is read/preparation support, and automatic wiki-memory persistence is not the explicit page-edit safe-output contract requested in the October 7 maintainer direction.
Next action: implement/review that built-in create/update output with a separate trusted write path, fixed/allowlisted wiki target, bounded page paths/content, explicit credentials and failure reporting, and staged/no-change behavior. Verify existing-page edits and new-page creation without giving the primary agent write credentials. Existing custom output and repo-memory routes may inform the implementation but are not grounds to close this request. No wiki mutation was attempted.
Activity
pelikhan commentedon Oct 7, 2026
@copilot add
safe-outputs.edit-wiki-page(create/update is implied).pelikhan commentedon Oct 7, 2026
Status (2026-10-07; Maintainer direction): In the October 7 discussion, a maintainer requested
safe-outputs.edit-wiki-page, with creation and updates implied. The next step is to specify and implement that built-in safe output; the request does not establish that it has shipped.pelikhan commentedon Oct 16, 2026
Current-state refresher (2026-10-16): still relevant. Checked default-branch snapshot
0d15bd1, not just the issue's open status.Wiki checkout support exists in the checkout generator, but this is not a privileged create/update wiki safe output. The current safe-output configuration does not provide
edit-wiki-page. The related implementations in #29626 and #1080 are closed without merging; their descriptions should not be read as shipped support.The outstanding work remains the built-in create/update safe output requested in the October 7 maintainer comment, including its trusted write path and policy validation. This is a source/history assessment; no workflow execution was attempted.
pelikhan commentedon Oct 22, 2026
2026-10-22 assessment: still relevant; no built-in
safe-outputs.edit-wiki-page.The current
SafeOutputsConfigstill has no wiki create/update output. The implementations #29626 and #1080 remain closed unmerged.There are related shipped capabilities, but they are not this API: #28900 added wiki checkout; #19800 added wiki-backed repo-memory; #36818 corrected its changed-file limit. Checkout is read/preparation support, and automatic wiki-memory persistence is not the explicit page-edit safe-output contract requested in the October 7 maintainer direction.
Next action: implement/review that built-in create/update output with a separate trusted write path, fixed/allowlisted wiki target, bounded page paths/content, explicit credentials and failure reporting, and staged/no-change behavior. Verify existing-page edits and new-page creation without giving the primary agent write credentials. Existing custom output and repo-memory routes may inform the implementation but are not grounds to close this request. No wiki mutation was attempted.