Skip to content

Comments

Update safe outputs spec with templatable boolean and integer fields#17694

Merged
pelikhan merged 2 commits intomainfrom
copilot/update-safe-output-spec
Feb 22, 2026
Merged

Update safe outputs spec with templatable boolean and integer fields#17694
pelikhan merged 2 commits intomainfrom
copilot/update-safe-output-spec

Conversation

Copy link
Contributor

Copilot AI commented Feb 22, 2026

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

  • GP1 / TS2 footer: Updated syntax to true | false | <github-expression>
  • TS1 max: Updated syntax to <positive-integer> | -1 | null | <github-expression>; added expression bullet to Special Values
  • New §5.5 — Templatable Fields: Formalizes the concept with conformance requirements for both field categories:
    • Templatable integers (max): expression resolved at runtime as integer; non-integer result MUST fail
    • Templatable booleans (footer, 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 as false
  • Appendix F: Version bump to 1.14.0
create-issue:
  max: ${{ inputs.max-issues }}       # templatable integer
  group: ${{ inputs.group-issues }}   # templatable boolean
  footer: ${{ inputs.enable-footer }} # templatable boolean
Original prompt

Update safe output spec with templetable Boolean and integer fields

See recent commits with support for templetables

Custom agent used: w3c-specification-writer
AI technical specification writer following W3C conventions and best practices for formal specifications


💡 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.

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 pelikhan marked this pull request as ready for review February 22, 2026 12:48
Copilot AI review requested due to automatic review settings February 22, 2026 12:48
@pelikhan pelikhan merged commit 7e83b9f into main Feb 22, 2026
69 checks passed
@pelikhan pelikhan deleted the copilot/update-safe-output-spec branch February 22, 2026 12:48
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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) and max (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):
Copy link

Copilot AI Feb 22, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Copilot uses AI. Check for mistakes.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants