mirror of
https://github.com/runkids/skillshare.git
synced 2026-11-20 20:34:19 +00:00
config.yaml records which skills a project wants, but not which commit each one resolved to, so two teammates running `install -p` a week apart could end up with different skill contents. Project mode now writes .skillshare/skills.lock.json next to the config. `install -p` checks out the locked commit for skills and tracked repos, and brings an already installed skill to the lock when they differ. `update -p` and the dashboard move a pin only for skills whose commit actually changed, so a stale local copy cannot roll the team back, and uninstall drops the pin. A locked value is only honoured when it is a full SHA for the same source, since it ends up as a git argument.