generated from eblume/project-template
Extract heph.nvim into its own forge repo #3
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feature/extract-heph-nvim"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The Neovim plugin now lives in its own repo, eblume/hephaestus.nvim (plugin at the repo root, so lazy.nvim loads it from a bare git URL). This removes
heph.nvim/from the monorepo and rewires the CI/docs that referenced it.Removed
heph.nvim/(14 Lua modules +plugin/heph.lua+ 16 e2e files) — now in the plugin repotest_nvimfunction + the pinnedNVIM_VERSIONdagger call test-nvimstep inbuild.yamlmise run test-nvimtask,.stylua.toml, and the stylua prek hook (no Lua remains here)Updated
install-heph.md§2 — install via a plain lazy.nvim spec over SSH (no more local-dir checkout hack)README/AGENTS/heph-nvim.md— note the surface lives in its own repo; the reference card keeps the architecture, points at the plugin repo for sources + e2eUnchanged (intentionally)
heph-tui,heph/service.rs) still shells out tonvimexpecting thehephplugin installed via lazyVerification
$HEPHD_BIN)prek run --all-filesclean here;.daggermodule compiles; no danglingtest-nvim/stylua/heph.nvim/references outside frozen historyNote
This drops the monorepo's headless-nvim CI coverage (it moves to the plugin repo, run locally against
$HEPHD_BIN). A future option: have the plugin repo's CI fetch a releasedhephdbinary once the monorepo publishes them.Independent of #2 (pre-v1 cleanup) — no overlapping files.
The recent CI failures ("Cannot connect to the Docker daemon") are the DinD build engine being OOM-killed mid-compile, not flakiness. Even 4 parallel rustc invocations spike memory too high on the runner; serialize to jobs=1. Slower but survives. Temporary mitigation pending more host RAM. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>