Skip to content

Knowledge sync (knowledge-sync.yaml)

Gha workflowreferenceworkflows/knowledge-sync

Checked by automation only

still a draft

Written 2026-10-28 by ktl-librarian (automation). Last checked 2026-10-28 by ktl-librarian (automation).

The full record
Checks
  • 2026-10-28 by ktl-librarian (automation)
Sources
Related to
Graph
Open this concept in the knowledge graph
IRI
https://w3id.org/lmodel/github-actions/knowledge/workflows/knowledge-sync
Licence
CC BY 4.0
Files
MarkdownJSON-LDSource on GitHubHistory on GitHub

.github/workflows/knowledge-sync.yaml is the workflow named “Knowledge sync”. A header comment says that it keeps the sidecar’s copies and the skills pin at the newest release of the Knowledge Trust Ladder (KTL) repository, which publishes the skills.1 NOTICE says that it is a copy of a ktl-sidecar template from that repository.2 It runs by hand and every Monday at 04:10 UTC, so that the librarian’s Monday run follows a current pin once the pull request is merged. It runs no LLM or agent and no code from the release, and it never pushes to the default branch or merges.

  • earlier reads the pin in knowledge-librarian.yaml, the newest KTL release, and the state of the workflow’s branch and last pull request, with contents: read and pull-requests: read. It is skipped in the KTL repository itself.
  • sync runs when the pin is behind, under a read-only token. It runs the host’s own .lokf/scripts/knowledge-sync.sh, which clones the release, reads its knowledge-sync.manifest, copies the templates over the host’s copies, moves the pin and writes the changelog entry.
  • publish applies the change with the default branch’s copy of the script, which refuses any path or change a sync may not make, and opens or refreshes one pull request from the knowledge-sync branch. It pushes with the KNOWLEDGE_SYNC_TOKEN secret, because the pin is under .github/workflows/, which the job’s own token may not push. Without the secret it attaches the patch to the run and opens nothing.
  • review and push-workflows are optional. The workflow changes a release brings are held, not pushed, and a person applies them after reading them. With KNOWLEDGE_SYNC_REVIEW_ENVIRONMENT naming an Environment with required reviewers, review waits for a reviewer and push-workflows then pushes the changes as a second commit.

CONTRIBUTING.md says that when TRUST_LADDER_SKILLS_REF moves in knowledge-librarian.yaml, the other knowledge-*.yaml workflows, .lokf/scripts/ and .lokf/m365/ move with it, copied from that release’s skills/ktl-sidecar/templates/ in the same pull request.3

  1. .github/workflows/knowledge-sync.yaml, the header comment, the on key and the five jobs ↩

  2. NOTICE, the Knowledge bundle section ↩

  3. CONTRIBUTING.md, the item on the skills pin ↩