All posts

· The LVCS team · 2 min read

CI that doesn't check githubstatus.com first

Your tests run on your machines, sign what they find, and skip anything that didn't change. Yes, that means fixing a README typo no longer reruns the whole integration suite. Already wrote GitHub workflows? Bring them. LVCS runs the jobs. No runner minutes. No “Waiting for a runner to pick up this job.” No “1 workflow awaiting approval.”

Example board
ChannelVersionAgreedHow it got thereStatus
CI3F9A0C3 / 3tests, lint, and build passed on 3 of 3 runnersMoved
OPENAPI3F9A0C1 / 1runs when ci moves: regenerates openapi.jsonMoved
RELEASE1C07E21 / 1runs when you say so: lvcs run releaseWaiting

A channel moves when its runners agree. Not before, and not on "probably fine."

Meanwhile, at githubstatus.com.

68 Actions incidents in 2026, and it's only October. That's 152 hours of “We are investigating reports of degraded performance.” 19 were critical, a label GitHub used twice from 2019 through 2025, so it's really getting into it now. The chart is GitHub's own data. We just added yellow.

GitHub Actions incidents per year, by GitHub's own impact label
  • Minor
  • Major
  • Critical
040802020: 9 Actions incidents, 21.4 hours; 9 minor, 0 major, 0 critical920202021: 41 Actions incidents, 88.6 hours; 34 minor, 7 major, 0 critical4120212022: 46 Actions incidents, 86 hours; 39 minor, 7 major, 0 critical4620222023: 59 Actions incidents, 111.7 hours; 46 minor, 12 major, 1 critical5920232024: 33 Actions incidents, 61.1 hours; 25 minor, 8 major, 0 critical3320242025: 48 Actions incidents, 90 hours; 37 minor, 11 major, 0 critical4820252026 (through 10-28): 68 Actions incidents, 152.3 hours; 33 minor, 16 major, 19 critical682026*

* 2026 runs through 2026-10-28. Source: GitHub's status page, githubstatus.com: every declared incident, with GitHub's own Actions component filter (history.json?filter=br0l2tvcx85d) plus incidents whose name contains the word Actions. Hours are declared-to-resolved time. Impact is GitHub's own label. 2020 counts are a lower bound: the Actions component was first used on 2020-04-14.

Show the numbers
YearActions incidentsHoursMinorMajorCriticalAll GitHub incidents
2020921.490070
20214188.6347086
202246863970123
202359111.746121164
20243361.12580124
2025489037110199
2026*68152.3331619254

Actions

CI is just actions plus channels. Each action is an [[actions]] entry in the project's lvcs.toml: one command, run on every machine you trust to run it.

tomlon main
1[[actions]]2name  = "auth"3paths = ["src/auth/**"]4uses  = ["src/token/**"]5run   = ["cargo", "test", "-p", "auth"]67[[actions]]8name  = "openapi"9on    = { channel = "ci" }10paths = ["src/**"]11run   = ["node", "scripts/openapi.mjs"]1213[[actions]]14name  = "release"15on    = "manual"16run   = ["sh", "scripts/release.sh"]

An action runs on change (every new version of main, the default, and what moves ci), on { channel = "<name>" } (when that channel moves), or on manual (lvcs run <action>). Each action's results move its own channel, named for the action.

Each action runs once per version, signs its result, and gets reused until its inputs change. ci moves when runners agree. Other actions can follow it. Every key is in the lvcs.toml reference.

Saved to mainNovember 1, 2026 · The LVCS team