Files
atuin/.buildkite/scripts/vale.sh
T
Ellie HuxtableandClaude Opus 5.5 c7f0318eb3 ci: run CI on Buildkite (#4274)
Move atuin's CI over to Buildkite. I've removed a few jobs from branches
and pushed them onto main, mostly things like the nixos build, illumos
etc - they were really slow, and difficult to optimise.

The goal is to be on buildkit, and have CI take around a minute per
commit. Once we have more tests, we can keep parallelizing

I tested out both the nvme disks and the buildkite cache. The former is
much faster, but is trickier to isolate across branches. I would prefer
that there is 0 chance of a branch messing with a build on main, or with
another branch.

---------

Co-authored-by: Claude Opus 5.5 (1M context) <[email protected]>
2026-09-26 17:45:57 -07:00

16 lines
559 B
Bash
Executable File

#!/usr/bin/env bash
# Lints the docs prose as .github/workflows/vale.yml did: vale-action with
# `--minAlertLevel=warning` and reviewdog's fail_on_error, which fails on any
# reported alert. Vale alone only exits non-zero on errors, so fail on any
# output instead.
set -euo pipefail
vale sync
out=$(vale --output=line --minAlertLevel=warning docs/docs || true)
if [ -n "$out" ]; then
echo "$out"
echo "+++ :rotating_light: Vale reported $(printf '%s\n' "$out" | wc -l | tr -d ' ') warning(s) or error(s)"
exit 1
fi
echo "Vale: no warnings or errors."