Trigger CI on next, not only main (closes #122)

`check.yml` ran only on push to `main` and on pull requests against `main`. Every unit is a PR based on `next`, and `next` is pushed on each squash-merge, so no unit PR and no push to `next` ever ran CI; a broken `next` would first surface on the milestone PR. `next` is added to both branch lists; nothing else in the workflow changes. The README Entrypoints section now says where CI runs. Disclosure: the CI run on the PR itself fired (the proof the trigger works) but was red because the runner had no disk space left before any check step ran; the local gate was green. Model: opus-4-8 (implementation and review) model: claude-fable-5
2026-09-21 14:55:59 +02:00
parent 583f65040a
commit d2a0510cb4
3 changed files with 10 additions and 2 deletions
@@ -25,6 +25,12 @@ release" is exactly the contradiction

 # Completed Steps

+- 2026-09-21: Made `.gitea/workflows/check.yml` run on pushes to `main`
+  and `next` and on pull requests against either, so unit PRs (whose
+  base is `next`) and `next` itself get a CI run instead of relying on a
+  local `make check`
+  ([issue #122](https://git.eeqj.de/sneak/vaultik/issues/122)).
+
 - 2026-08-10: Moved every lint run into its own container, as a build
  step ([issue #113](https://git.eeqj.de/sneak/vaultik/issues/113)).
  New root `Dockerfile.lint`, built by `script/lint`, runs