docs: fix documentation drift in front-matter.md from recent PRs#423
Merged
jamesadevine merged 1 commit intomainfrom May 6, 2026
Merged
docs: fix documentation drift in front-matter.md from recent PRs#423jamesadevine merged 1 commit intomainfrom
jamesadevine merged 1 commit intomainfrom
Conversation
Agent-Logs-Url: https://github.com/githubnext/ado-aw/sessions/ce99543c-dacc-4e66-ae3d-7d811d603b42 Co-authored-by: jamesadevine <4742697+jamesadevine@users.noreply.github.com>
Copilot created this pull request from a session on behalf of
jamesadevine
May 6, 2026 16:03
View session
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.
Three issues in
docs/front-matter.mdintroduced by PRs #400 and #409.Summary
on:key (PR fix(compile): reject unknown front-matter fields with deny_unknown_fields #409 regression): Movingschedule:underon:added a secondon:block near the top of the example YAML while the fullon:trigger block already existed further down — invalid YAML with two identical top-level keys. Removed the spurious first block.workspace: repo# Optional:→workspace: repo # Optional:docs/runtimes.md, but theruntimes:section in thefront-matter.mdreference example still only showedlean:. Added commentedpython:andnode:examples inline.Test plan
Documentation-only change; no code modified.