3 Commits

Include renames

Author	SHA1	Message	Date
clawbot	6aac45857a	Cancel replaced CI runs and drop the checkout token (closes #107) ... The canonical `.gitea/workflows/check.yml` lacked two settings `dnswatcher` had added, so a byte-identical re-vendor removed them. A `concurrency` block grouped by workflow and branch, with `cancel-in-progress: true`, makes a new push cancel the older run on the same branch and leaves every other branch's runs alone; on 2026-10-02 45 stale runs had queued on the one shared runner. `persist-credentials: false` on the checkout step keeps the job's token out of `.git/config`; `script/cibuild` needs no token. Each has a one-line comment, and the policy's workflow bullet and both checklists describe the file as it now is. Unverified: the two live checks, which wait on the shared runner. Model: opus-5-5	2026-10-06 05:52:57 +02:00
sneak	3d8d1c0600	Adopt scripts-to-rule-them-all: script/ entrypoints, Makefile shims, policy update (#23) ... Reviewed-on: #23 Co-authored-by: sneak <sneak@sneak.berlin> Co-committed-by: sneak <sneak@sneak.berlin>	2026-07-06 23:53:05 +02:00
sneak	f43445caea	Add CI policy, strengthen hash-pinning rule, add Gitea Actions workflow ... - All Dockerfiles must run make check as a build step - Every repo needs a Gitea Actions workflow running docker build on push - Greatly strengthen the hash-pinning rule: explicitly list all reference types, ban curl|bash installs, mark as most important rule in document - Add model .gitea/workflows/check.yml pinned by commit hash	2026-02-22 16:35:42 +01:00