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 clawbot2026-08-11 14:15:31 +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.
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 fromnext, one PR per issue based onnext, squash-merged intonext, andmainreached only by the per-milestone PR.TODO.mdwas corrected to the current model in #191;RULES.mdnow contradicts it.RULES.mdis owner-only, so no agent edited it.Proposed replacement for that line:
> Branch per issue, cut from
next. One PR per issue, based onnext, squash-merged intonexton a passed independent review.mainis reached only by the per-milestone PR fromnext; releases are tagged frommain.nextandmainmust 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.mdis 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 againstRULES.md.