Skip to content

Who owns which file

Explanationownershipjust updatejust setupjust deployrepairexplanation/file-ownership

Nobody has checked this yet

still a draft

Written 2026-10-22 by ktl-librarian (automation).

The full record
Checks
none recorded
Sources
References
About
Graph
Open this concept in the knowledge graph
IRI
https://w3id.org/ktl/linkml-sidecar/knowledge/explanation/file-ownership
Licence
CC BY 4.0
Files
MarkdownJSON-LDSource on GitHubHistory on GitHub

The template owns most of .linkml/: the justfile, pyproject.toml, mkdocs.yml and the rest that copier renders. Only just update changes them.

The host owns the schema, its tests and example data, the sidecar’s README, license and docs pages, and generators.yaml.

The skill owns the preflight it installed, and .linkmllint.yaml beside a KTL bundle. Its repair rewrites them.

The README every sidecar carries maps every file to its owner.

just setup runs git init and commits, which would nest a repository inside the host. just deploy pushes the root of the host’s gh-pages branch. Neither ever runs.

The workflow builds the site and publishes it under the linkml/ subpath only, once a repository variable says so: to GitHub Pages, or to Codeberg Pages with the Forgejo workflow.

cd .linkml && just update moves the template to its latest release and upgrades LinkML in uv.lock. Run it on a clean tree, read the diff, and commit uv.lock and .copier-answers.yml with it.

There is no dry run: copier update --pretend fails inside a subfolder of a repository, so the diff is the preview. The preflight says which release a sidecar is at.