decision: RULES.md "Build & Workflow" still says merge to main, contradicting the branch-per-issue-onto-next model #193

Open
opened 2026-08-11 14:15:31 +02:00 by clawbot · 0 comments
Collaborator

RULES.md "Build & Workflow" reads "Feature branches for all changes, merge to main when done". That is no longer what the repo does: branch per issue from next, one PR per issue based on next, squash-merged into next, and main reached only by the per-milestone PR. TODO.md was corrected to the current model in #191; RULES.md now contradicts it.

RULES.md is owner-only, so no agent edited it.

Proposed replacement for that line:

> Branch per issue, cut from next. One PR per issue, based on next, squash-merged into next on a passed independent review. main is reached only by the per-milestone PR from next; releases are tagged from main. next and main must stay green; feature branches may be red.

Options: (a) apply the wording above; (b) apply different wording you prefer; (c) leave it and accept the contradiction.

Recommendation: (a) — it states the model already in force, and RULES.md is the document agents are pointed at first, so a stale line there misdirects every future worker. Say the word and I will open the PR against RULES.md.

`RULES.md` "Build & Workflow" reads "Feature branches for all changes, merge to main when done". That is no longer what the repo does: branch per issue from `next`, one PR per issue based on `next`, squash-merged into `next`, and `main` reached only by the per-milestone PR. `TODO.md` was corrected to the current model in https://git.eeqj.de/sneak/AutistMask/issues/191; `RULES.md` now contradicts it. `RULES.md` is owner-only, so no agent edited it. Proposed replacement for that line: > Branch per issue, cut from `next`. One PR per issue, based on `next`, squash-merged into `next` on a passed independent review. `main` is reached only by the per-milestone PR from `next`; releases are tagged from `main`. `next` and `main` must stay green; feature branches may be red. Options: (a) apply the wording above; (b) apply different wording you prefer; (c) leave it and accept the contradiction. Recommendation: (a) — it states the model already in force, and `RULES.md` is the document agents are pointed at first, so a stale line there misdirects every future worker. Say the word and I will open the PR against `RULES.md`.
sneak was assigned by clawbot 2026-08-11 14:15:31 +02:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sneak/AutistMask#193