From e823147193dc3069d8526200c4e28bd755c3624d Mon Sep 17 00:00:00 2001 From: sneak Date: Mon, 21 Sep 2026 07:23:27 +0000 Subject: [PATCH] Trigger CI on next, not only main (closes #122) check.yml ran only on push to main and pull_request against main. Under the current workflow every unit is a PR based on next, and next is pushed to on each squash-merge, so neither got a CI run; the milestone PR from next to main was the first place a broken next would surface. Add next to both the push and pull_request branch lists so unit PRs and next itself are checked. The workflow is otherwise unchanged: same pinned actions/checkout sha, same script/cibuild step. README's Entrypoints section and TODO.md's log record where CI now runs. Model: opus-4-8 --- .gitea/workflows/check.yml | 4 ++-- README.md | 2 ++ TODO.md | 6 ++++++ 3 files changed, 10 insertions(+), 2 deletions(-) diff --git a/.gitea/workflows/check.yml b/.gitea/workflows/check.yml index 0a914ad..b4e58dc 100644 --- a/.gitea/workflows/check.yml +++ b/.gitea/workflows/check.yml @@ -1,9 +1,9 @@ name: check on: push: - branches: [main] + branches: [main, next] pull_request: - branches: [main] + branches: [main, next] jobs: check: runs-on: ubuntu-latest diff --git a/README.md b/README.md index 89e4697..9e17b9c 100644 --- a/README.md +++ b/README.md @@ -716,6 +716,8 @@ them. We provide: then the product image). Either failing fails the script. It runs the checks in the same containers CI does, from a clean copy of the tree, so it also catches anything that depends on host state. + `.gitea/workflows/check.yml` runs it on every push to `main` and + `next` and on every pull request against either. It passes a fresh `--build-arg CHECK_EPOCH` to each build, unique per invocation, which both files declare immediately above their check diff --git a/TODO.md b/TODO.md index e05ed56..3f2ef0d 100644 --- a/TODO.md +++ b/TODO.md @@ -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