Update safe outputs spec with templatable boolean and integer fields#17694
Merged
Update safe outputs spec with templatable boolean and integer fields#17694
Conversation
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Update safe output spec with templetables support
Update safe outputs spec with templatable boolean and integer fields
Feb 22, 2026
pelikhan
approved these changes
Feb 22, 2026
Contributor
There was a problem hiding this comment.
Pull request overview
This PR updates the Safe Outputs MCP Gateway Specification to document that several configuration fields support GitHub Actions expressions (e.g., ${{ inputs.max-issues }}) in addition to literal values—a feature already present in the implementation but previously undocumented.
Changes:
- Added new Section 5.5 "Templatable Fields" with formal conformance requirements for templatable integers and booleans
- Updated syntax definitions for
footer(GP1, TS2) andmax(TS1) to include<github-expression>alternative - Added version 1.14.0 entry to Appendix F documenting these changes
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
|
||
| ## Appendix F: Document History | ||
|
|
||
| **Version 1.14.0** (2026-02-22): |
There was a problem hiding this comment.
The document version header needs to be updated to 1.14.0 to match the version history added in Appendix F. Currently the header shows version 1.13.0 but Appendix F documents this as version 1.14.0.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The safe outputs specification didn't document that several configuration fields accept GitHub Actions expressions (e.g.,
${{ inputs.max-issues }}) in addition to literal values — a capability already supported in the implementation.Changes
footer: Updated syntax totrue | false | <github-expression>max: Updated syntax to<positive-integer> | -1 | null | <github-expression>; added expression bullet to Special Valuesmax): expression resolved at runtime as integer; non-integer result MUST failfooter,group,close-older-issues,hide-older-comments,close-older-discussions,draft,allow-empty,auto-merge,report-as-issue,unassign-first): free-form strings rejected at compile time; non-boolean runtime value treated asfalseOriginal prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.