CI: no quick check on master after a merge #119

New Issue

2026-11-06T20:42:31Z

rajames commented

2026-11-06 20:42:31 +00:00

What

build.yml runs on pushes to the working branch only, not on master.

Why

Captain Bob, 2026-11-06: a small server, a little sluggish. Each change costs about an hour of runner time, of which the gate itself (acceptance) is about 15 minutes. Every commit that reaches master arrives through a PR whose content has just passed acceptance (branch protection), so the ~23-minute quick check that build.yml runs on master after every merge checks content already checked.

Done when

build.yml triggers on pushes to the working branch, and by hand
A merge into master starts no quick check

## What `build.yml` runs on pushes to the working branch only, not on `master`. ## Why Captain Bob, 2026-11-06: a small server, a little sluggish. Each change costs about an hour of runner time, of which the gate itself (acceptance) is about 15 minutes. Every commit that reaches `master` arrives through a PR whose content has just passed acceptance (branch protection), so the ~23-minute quick check that `build.yml` runs on `master` after every merge checks content already checked. ## Done when - [ ] `build.yml` triggers on pushes to the working branch, and by hand - [ ] A merge into `master` starts no quick check

rajames added this to the CI and the gate milestone 2026-11-06 20:42:31 +00:00

rajames added the

labels 2026-11-06 20:42:31 +00:00

rajames referenced this issue from a commit

2026-11-06 21:44:20 +00:00

ci: no quick check on master after a merge (#119); the runner image's recipe (#120)