Repository navigation
refactor(ci): share build and plugin restore via a composite action - #57
Merged
Merged
Conversation
A bare `Lazy! restore` on a cache miss lets lazy.nvim's first-run install rewrite the lockfile before LazyVim's imported specs are known, leaving those plugins at their upstream target. Install first, copy the committed lock back, restore, and cmp the result -- the same sequence lazy-update.yml uses. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…/ci-fresh-restore
…tor/ci-shared-setup
ci.yml's test job and lazy-update.yml both built a kapi-vim package, put it on PATH and ran the checked lazy.nvim restore, with the restore sequence and its comment duplicated. .github/actions/setup-kapi-vim now does all three, plus the plugin cache. The cache is split into restore/save so lazy-update can read CI's cache without writing its updated plugins under the old lockfile's key; the save also moves to straight after the checked restore. The key changes from runs-on to OS/arch since a composite action can't see the matrix, so the first run after this misses once. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Owner
Author
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
1 participant
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.
ci.yml's test job andlazy-update.ymlboth build a kapi-vim package, put its nvim on PATH and run the checked lazy.nvim restore. After #53 and #54, the restore sequence and its explanation were duplicated word for word. A composite action,.github/actions/setup-kapi-vim, now does all of that plus the plugin cache. Both workflows call it.A composite action rather than a reusable workflow: lazy-update has to run its own update step between the restore and the smoke test, so the shared unit is a block of steps, not a whole job.
actions/cacheis nowcache/restorepluscache/save. lazy-update passessave-cache: 'false', so it can read CI's cache but never stores its bumped plugins under the old lockfile's key. The save also moves from job end to straight after the checked restore, so the cache only ever holds exactly the locked plugins.matrix.runs-ontorunner.os/runner.archbecause a composite action can't see the matrix. Still platform-specific, which telescope-fzf-native needs.ci.ymlstep (moved into the action here).🤖 Generated with Claude Code