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.”
| Channel | Version | Agreed | How it got there | Status |
|---|---|---|---|---|
| CI | 3F9A0C | 3 / 3 | tests, lint, and build passed on 3 of 3 runners | Moved |
| OPENAPI | 3F9A0C | 1 / 1 | runs when ci moves: regenerates openapi.json | Moved |
| RELEASE | 1C07E2 | 1 / 1 | runs when you say so: lvcs run release | Waiting |
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.
- Minor
- Major
- Critical
* 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
| Year | Actions incidents | Hours | Minor | Major | Critical | All GitHub incidents |
|---|---|---|---|---|---|---|
| 2020 | 9 | 21.4 | 9 | 0 | 0 | 70 |
| 2021 | 41 | 88.6 | 34 | 7 | 0 | 86 |
| 2022 | 46 | 86 | 39 | 7 | 0 | 123 |
| 2023 | 59 | 111.7 | 46 | 12 | 1 | 164 |
| 2024 | 33 | 61.1 | 25 | 8 | 0 | 124 |
| 2025 | 48 | 90 | 37 | 11 | 0 | 199 |
| 2026* | 68 | 152.3 | 33 | 16 | 19 | 254 |
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.
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
Read nextNever click “Update branch” again