ci: run vale from flake.lock instead of the moving nixpkgs registry
This commit is contained in:
parent
26c4ff89d5
commit
d1d874770b
1 changed files with 4 additions and 3 deletions
|
|
@ -79,7 +79,7 @@ jobs:
|
|||
- uses: actions/checkout@v3
|
||||
- name: lint
|
||||
# `nix develop` enters the whole devshell for this one tool, which pins
|
||||
# shellcheck to flake.lock; the vale and jq jobs take theirs from the registry.
|
||||
# shellcheck to flake.lock; the jq job takes its own from the registry.
|
||||
#
|
||||
# By shebang, not a `*.sh` glob — scripts/pre-push has no suffix.
|
||||
run: |
|
||||
|
|
@ -97,10 +97,11 @@ jobs:
|
|||
steps:
|
||||
- uses: actions/checkout@v3
|
||||
- name: lint
|
||||
# The vale binary comes from flake.lock (`--inputs-from .`), like the devshell's.
|
||||
# Styles are fetched fresh from Vale Package Hub each run (not vendored).
|
||||
# Not wired into branch protection — see prose-lint-errors below for the
|
||||
# error-only slice that is.
|
||||
run: XDG_DATA_HOME="$PWD/.vale-data" nix shell nixpkgs#vale --command sh -c 'vale sync && vale docs'
|
||||
run: XDG_DATA_HOME="$PWD/.vale-data" nix shell --inputs-from . nixpkgs#vale --command sh -c 'vale sync && vale docs'
|
||||
|
||||
prose-lint-errors:
|
||||
name: prose lint (vale, errors)
|
||||
|
|
@ -111,4 +112,4 @@ jobs:
|
|||
- name: lint
|
||||
# Error-level-only slice. Split out so this job alone can be a required
|
||||
# check without blocking merges on the warning/suggestion backlog.
|
||||
run: XDG_DATA_HOME="$PWD/.vale-data" nix shell nixpkgs#vale --command sh -c 'vale sync && vale --minAlertLevel=error docs'
|
||||
run: XDG_DATA_HOME="$PWD/.vale-data" nix shell --inputs-from . nixpkgs#vale --command sh -c 'vale sync && vale --minAlertLevel=error docs'
|
||||
|
|
|
|||
Loading…
Reference in a new issue