Remove payload-dir from frontmatter documentation#14069
Merged
Conversation
The payload-dir field was never user-configurable from workflow frontmatter. It's an internal implementation detail set programmatically by ensureDefaultMCPGatewayConfig(). The extractMCPGatewayConfig() function does not extract this field from frontmatter. The payloadDir field remains correctly documented in the MCP Gateway Specification (mcp-gateway.md) as part of the gateway configuration JSON schema, which is the correct location for internal gateway configuration. Changes: - Removed payload-dir section from frontmatter.md - No code changes needed (field was never parsed from frontmatter) - PayloadDir field in MCPGatewayRuntimeConfig remains unchanged (internal use) - MCP gateway specification documentation unchanged (correct location) Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Remove payload-dir from frontmatter and documentation
Remove payload-dir from frontmatter documentation
Feb 6, 2026
This was referenced Feb 6, 2026
Contributor
🔍 PR Triage ResultsCategory: docs | Risk: low | Priority: 27/100 Scores Breakdown
📋 Recommended Action: DeferDraft PR - defer until marked ready for review. Complete testing and validation, then mark as ready. Triaged by PR Triage Agent on 2026-02-06
|
Contributor
There was a problem hiding this comment.
Pull request overview
This PR corrects documentation by removing the payload-dir field from the frontmatter reference documentation. The field was incorrectly documented as a user-configurable frontmatter option, but it is actually an internal implementation detail that is set programmatically and never extracted from frontmatter.
Changes:
- Removed the
payload-dirsection from frontmatter.md that incorrectly suggested users could configure this field - No code changes were needed since the field was never extracted from frontmatter
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
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
payload-dirfield was documented as a user-configurable frontmatter option, butextractMCPGatewayConfig()never parses it from frontmatter. The field is set programmatically byensureDefaultMCPGatewayConfig()to/tmp/gh-aw/mcp-payloadsand is an internal implementation detail.Changes
payload-dirsection fromdocs/src/content/docs/reference/frontmatter.mdpayloadDirdocumentation inmcp-gateway.mdwhere it correctly appears as part of the gateway configuration JSON schemaThe field remains properly documented in the MCP Gateway Specification as an internal gateway config parameter, which is its correct location.
Original prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.