mirror/nix-community.nixvim
1
0
Fork 0
mirror of https://github.com/nix-community/nixvim.git synced 2025-07-09 08:44:32 +02:00
Code Issues Projects Releases Packages Wiki Activity Actions 4
nix-community.nixvim/ci
History
Matt Sturgeon bc997a2409
Some checks are pending
Publish every Git push to main to FlakeHub / flakehub-publish (push) Waiting to run
Details
Publish every git push to Flakestry / publish-flake (push) Waiting to run
Details
Documentation / Version info (push) Waiting to run
Details
Documentation / Build (push) Blocked by required conditions
Details
Documentation / Combine builds (push) Blocked by required conditions
Details
Documentation / Deploy (push) Blocked by required conditions
Details
ci/version-info: create temp files in a temp directory 
Avoid polluting the repo with temporary `channels.{nix,json,toml}`
files. Write them to a temporary working directory instead.
2025-07-07 16:10:55 +00:00
..
nvim-lspconfig ci: rename update-scripts → ci 2025-06-15 21:23:58 +00:00
rust-analyzer ci: rename update-scripts → ci 2025-06-15 21:23:58 +00:00
version-info ci/version-info: create temp files in a temp directory 2025-07-07 16:10:55 +00:00
default.nix ci: rename update-scripts → ci 2025-06-15 21:23:58 +00:00
efmls-configs.nix ci/efmls-configs: merge language sets with different cases 2025-06-25 19:20:44 +00:00
generate.nix ci: rename update-scripts → ci 2025-06-15 21:23:58 +00:00
none-ls.nix ci: rename update-scripts → ci 2025-06-15 21:23:58 +00:00
README.md ci: rename update-scripts → ci 2025-06-15 21:23:58 +00:00
shell.nix ci: rename update-scripts → ci 2025-06-15 21:23:58 +00:00
update.nix ci: rename update-scripts → ci 2025-06-15 21:23:58 +00:00

README.md

CI scripts

This directory contains CI-related scripts that are not part of the actual flake. Unless developing or testing changes, you shouldn't need to run them manually.

Developing

Because these scripts aren't packaged in the flake, you should use nix-build and nix-shell instead of nix build, nix run, and nix develop, etc.

For example, nix-build -A generate will build ./generate.nix into ./result/bin/generate.

A shell.nix is available that will place generate on your PATH.

You could use this directory's shell/packages from another working directory by supplying nix-build or nix-shell with a path. E.g. nix-shell ./ci.

Explanation

These packages are not in the flake outputs for three main reasons:

  • Packages built using the flake must follow the flake's nixConfig
  • Packages included in the flake's output are checked by nix flake check
  • Some of the packages should have no dependency on the flake at all, allowing this directory to be sparse checked out by a workflow

Being unable to bypass nixConfig is an issue because we want to disable IFD for the flake, but not for these scripts.

If something changes upstream that causes the builds to fail, we don't want this to block us updating flake.lock. We'd still be made aware of any issues by the update CI workflow failing.