Template pin
glossary/template-pinChecked by automation only
still a draft
Written 2026-10-22 by ktl-librarian (automation). Last checked 2026-10-22 by ktl-librarian (automation).
The tag and commit of linkml-project-copier the sidecar is made from, held as LINKML_TEMPLATE_REF and LINKML_TEMPLATE_SHA in skills/linkml-sidecar/scripts/linkml-scaffold.sh and recorded in .copier-answers.yml as _commit.
The full record
- Checks
- 2026-10-22 by
ktl-librarian(automation)
- 2026-10-22 by
- Sources
- Pointed to by
- Contributing (references)
- linkml-project-copier (references)
- linkml-scaffold.sh (references)
- Repository contract (references)
- Who owns which file (references)
- Graph
- Open this concept in the knowledge graph
- IRI
https://w3id.org/ktl/linkml-sidecar/knowledge/glossary/template-pin- Licence
- CC BY 4.0
- Files
- MarkdownJSON-LDSource on GitHubHistory on GitHub
Overview
Section titled “Overview”The template pin is held in one place, the scaffold driver: LINKML_TEMPLATE_REF (the tag, v0.5.0) and LINKML_TEMPLATE_SHA (the commit it names). Before copier runs with --trust, the scaffold checks with git ls-remote that the tag still names that commit, so a moved tag stops the scaffold. A finished sidecar records the pin in .copier-answers.yml as _commit: v0.5.0.
The repository contract holds every other mention under skills/ and docs/, and in README.md and CONTRIBUTING.md, to these two values. Moving the pin is a contributor’s checklist item: change both values, re-walk the assumptions catalogue, re-run the slow tests, and update the Sources note in SKILL.md. In a host, cd .linkml && just update on a clean tree moves the template.