Repository navigation
docs(fork): a machine-readable header on every carried-change file - #720
Merged
Merged
Conversation
Every file under fork/carried/ opens with the YAML front-matter proposed in #719, seeded from the row and the 2026-10-19 state board; scripts/fork/carried.sh skips the front-matter before checking the row; FORK.md names the fields. Signed-off-by: QuentinBisson <[email protected]>
…ubstrate counterpart edges Signed-off-by: QuentinBisson <[email protected]>
The fork-ledger check runs scripts/fork/ledger-header.sh on fork/carried next to carried.sh --check, with its --self-test fixtures, the same rules as fork-ledger validate (#719). Signed-off-by: QuentinBisson <[email protected]>
QuentinBisson
marked this pull request as ready for review
October 19, 2026 12:11
QuentinBisson
added a commit
that referenced
this pull request
Oct 19, 2026
* docs(fork): ledger facts as of 2026-10-19 Signed-off-by: QuentinBisson <[email protected]> * docs(fork): the compiled-skills carried row superseded by upstream kagent-dev#3203 Signed-off-by: QuentinBisson <[email protected]> * docs(fork): a machine-readable header on every carried-change file (#720) * docs(fork): a machine-readable header on every carried-change file Every file under fork/carried/ opens with the YAML front-matter proposed in #719, seeded from the row and the 2026-10-19 state board; scripts/fork/carried.sh skips the front-matter before checking the row; FORK.md names the fields. Signed-off-by: QuentinBisson <[email protected]> * docs(fork): drop internal tracker numbers from the headers, add the Substrate counterpart edges Signed-off-by: QuentinBisson <[email protected]> * ci(fork): check the ledger header schema The fork-ledger check runs scripts/fork/ledger-header.sh on fork/carried next to carried.sh --check, with its --self-test fixtures, the same rules as fork-ledger validate (#719). Signed-off-by: QuentinBisson <[email protected]> --------- Signed-off-by: QuentinBisson <[email protected]> --------- Signed-off-by: QuentinBisson <[email protected]>
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.
Problem
The ledger files are prose tables, so nothing can read the
Upstreamcell of a carried change without a person, and the cells drift from GitHub between re-pins. #719 proposes a machine-readable header on every file.Change
Every
fork/carried/*.mdgets a YAML front-matter (id, fork, theme, category, status, upstream outcome/refs/exit, depends_on, commit, verified) seeded from the table cell and reviewed by hand;commitis the carried commit's SHA ongiantswarm, resolved from the subject. The table stays as it is until #719 settles whether the cell goes. Cross-linedepends_onentries name the counterpart file in the Substrate and agentgateway ledgers.scripts/fork/carried.shskips the front-matter; FORK.md describes the fields. Stacked on #718.