README development workflow: branch from and merge into next (closes #135)
check / check (push) Successful in 1m0s

"Development workflow" and "For LLMs" said work branches off main and merges into main. They now say work branches from next, every pull request targets next, the repository manager squash-merges reviewed pull requests into next once make check is green, and only sneak merges next into main. The rest of both sections is unchanged.

Docs only; merged under the docs-only rule without an adversarial review.

Model: opus-5-5
This commit was merged in pull request #136.
This commit is contained in:
2026-09-29 05:38:36 +02:00
parent e6a9e929c2
commit c27e2cb629
2 changed files with 19 additions and 10 deletions
+5
View File
@@ -22,6 +22,11 @@ declares one.
# Completed Steps
- 2026-09-29: The README's "Development workflow" and "For LLMs" sections now
say work branches from `next`, every pull request targets `next`, the
repository manager squash-merges reviewed pull requests into `next`, and only
sneak merges `next` into `main` (issue 135).
- 2026-09-29: Brought the README and this file in line with `next` after the
milestone merge (issue 132). The Next Step says no implementation work is open
and the cache design (issue 36) waits on sneak's review. README corrections: