Repository navigation
docs(fork): a machine-readable header on every carried-change file - #478
Merged
Merged
Conversation
Signed-off-by: QuentinBisson <quentin@giantswarm.io>
Every file under fork/ opens with the YAML front-matter proposed in giantswarm/kagent-upstream#719 (id, fork, theme, category, status, upstream outcome/refs/exit, depends_on, commit, verified), seeded from the prose and the 2026-10-19 review; the prose is unchanged. FORK.md describes the fields. Signed-off-by: QuentinBisson <quentin@giantswarm.io>
…eaders Signed-off-by: QuentinBisson <quentin@giantswarm.io>
Signed-off-by: QuentinBisson <quentin@giantswarm.io>
The fork-ledger workflow runs .github/scripts/ledger-header.sh on fork/ with its fixture test, the same rules as fork-ledger validate (giantswarm/kagent-upstream#719). Signed-off-by: QuentinBisson <quentin@giantswarm.io>
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
1 participant
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.
Problem
The ledger files are prose, so nothing can read the
Upstreamstate of a carried change without a person: a keyword pass over the agentgateway ledger agreed with a human reading on 11 of 20 files. giantswarm/kagent-upstream#719 proposes a machine-readable header on every file.Change
Every
fork/*.mdgets a YAML front-matter (id, fork, theme, category, status, upstream outcome/refs/exit, depends_on, commit, verified) seeded from the prose and reviewed by hand; the prose stays as it is, and theStatusandUpstreambullets stay beside the header until agent-substrate#719 settles whether they go. Cross-linedepends_onentries name the counterpart file in the other ledgers. FORK.md describes the fields. Stacked on #477.