README.md "Development workflow" says every change starts on a feature branch off main (item 1) and is merged into main when make check is green (item 4), and item 8 says a red branch cannot reach main. That is not how work lands. The settled policy is:
work branches from next;
every pull request targets next;
the repo-manager squash-merges reviewed units into next;
only sneak merges next into main.
The "For LLMs" section repeats the old flow: "make check (which also runs the tests) must pass before merging to main".
Definition of done
"Development workflow" states the four points above in plain sentences, replacing the main-based wording in items 1, 4 and 8. main and next are always green, and make check must be green before a unit is merged into next.
The "For LLMs" section's lines about where work branches from and merges into say the same.
The rest of the section (tests first, fixtures, commit clean-up, the pre-commit hook) is unchanged except where it names the branch.
Docs only: README.md, plus a Completed Steps entry at the top of TODO.md in the same commit. make fmt run on the changed markdown; make check green.
Model: opus-5-5
## Problem
`README.md` "Development workflow" says every change starts on a feature branch off `main` (item 1) and is merged into `main` when `make check` is green (item 4), and item 8 says a red branch cannot reach `main`. That is not how work lands. The settled policy is:
- work branches from `next`;
- every pull request targets `next`;
- the repo-manager squash-merges reviewed units into `next`;
- only sneak merges `next` into `main`.
The "For LLMs" section repeats the old flow: "make check (which also runs the tests) must pass before merging to `main`".
## Definition of done
1. "Development workflow" states the four points above in plain sentences, replacing the `main`-based wording in items 1, 4 and 8. `main` and `next` are always green, and `make check` must be green before a unit is merged into `next`.
2. The "For LLMs" section's lines about where work branches from and merges into say the same.
3. The rest of the section (tests first, fixtures, commit clean-up, the pre-commit hook) is unchanged except where it names the branch.
4. Docs only: `README.md`, plus a Completed Steps entry at the top of `TODO.md` in the same commit. `make fmt` run on the changed markdown; `make check` green.
Model: opus-5-5
clawbot
self-assigned this 2026-09-29 05:25:19 +02:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Problem
README.md"Development workflow" says every change starts on a feature branch offmain(item 1) and is merged intomainwhenmake checkis green (item 4), and item 8 says a red branch cannot reachmain. That is not how work lands. The settled policy is:next;next;next;nextintomain.The "For LLMs" section repeats the old flow: "make check (which also runs the tests) must pass before merging to
main".Definition of done
main-based wording in items 1, 4 and 8.mainandnextare always green, andmake checkmust be green before a unit is merged intonext.README.md, plus a Completed Steps entry at the top ofTODO.mdin the same commit.make fmtrun on the changed markdown;make checkgreen.Model: opus-5-5