Closes #191. Documentation only — TODO.md is the sole changed file.
Workflow now describes what the repo actually does: pull next and cut one branch per issue from it, one commit whose title ends with (closes #N) carrying the TODO.md update, rebase onto current next before pushing, one PR per issue with base 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 stay green while a feature branch may be red.
Status now names the 1.0.0 milestone in flight on next with its milestone PR #190, and points at the tracker as the authoritative backlog rather than duplicating it. Next Step names a real open item, #152.
Judgement calls:
Completed Steps was not rewritten. Two entries were appended: the build-time DEBUG flag (#149), which landed but had no entry, and this change. Existing entries keep their bare #N references untouched.
Future Steps was pruned to the three items that have no issue of their own (pre-1.0 security review, the docker-in-docker decision for make test-e2e in CI, cutting 1.0.0). Everything else there was already filed and is on the tracker.
RULES.md "Build & Workflow" still says "Feature branches for all changes, merge to main when done", which the new Workflow contradicts. RULES.md is owner-only and out of scope here; flagging it rather than editing it.
Verification: make fmt run, no change to TODO.md (already Prettier-clean). make check green on the rebased branch — 7 suites, 143 tests passed; prettier --check .: "All matched files use Prettier code style!" for both lint and fmt-check. Rebased onto origin/next at e9fa8be before pushing; no conflicts.
Closes https://git.eeqj.de/sneak/AutistMask/issues/191. Documentation only — `TODO.md` is the sole changed file.
Workflow now describes what the repo actually does: pull `next` and cut one branch per issue from it, one commit whose title ends with ` (closes #N)` carrying the `TODO.md` update, rebase onto current `next` before pushing, one PR per issue with base `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` stay green while a feature branch may be red.
Status now names the 1.0.0 milestone in flight on `next` with its milestone PR https://git.eeqj.de/sneak/AutistMask/pulls/190, and points at the tracker as the authoritative backlog rather than duplicating it. Next Step names a real open item, https://git.eeqj.de/sneak/AutistMask/issues/152.
Judgement calls:
- Completed Steps was not rewritten. Two entries were appended: the build-time `DEBUG` flag (https://git.eeqj.de/sneak/AutistMask/issues/149), which landed but had no entry, and this change. Existing entries keep their bare `#N` references untouched.
- Future Steps was pruned to the three items that have no issue of their own (pre-1.0 security review, the docker-in-docker decision for `make test-e2e` in CI, cutting 1.0.0). Everything else there was already filed and is on the tracker.
- `RULES.md` "Build & Workflow" still says "Feature branches for all changes, merge to main when done", which the new Workflow contradicts. `RULES.md` is owner-only and out of scope here; flagging it rather than editing it.
Verification: `make fmt` run, no change to `TODO.md` (already Prettier-clean). `make check` green on the rebased branch — 7 suites, 143 tests passed; `prettier --check .`: "All matched files use Prettier code style!" for both `lint` and `fmt-check`. Rebased onto `origin/next` at `e9fa8be` before pushing; no conflicts.
The Workflow section still described branching from `main` and merging
straight to it. It now describes what the repo actually does: one branch
and one PR per issue cut from and based on `next`, squash-merged into
`next` on a passed independent review, with `main` reached only by the
per-milestone PR from `next` and releases tagged from `main`.
Status and Next Step were stale (they named a branch that landed as
`23aeae4`). Status now points at the 1.0.0 milestone in flight and the
tracker as the authoritative backlog; Next Step names a real open item.
Future Steps keeps only work that has no issue of its own.
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.
Closes #191. Documentation only —
TODO.mdis the sole changed file.Workflow now describes what the repo actually does: pull
nextand cut one branch per issue from it, one commit whose title ends with(closes #N)carrying theTODO.mdupdate, rebase onto currentnextbefore pushing, one PR per issue with basenext, squash-merged intonexton a passed independent review.mainis reached only by the per-milestone PR fromnext, releases are tagged frommain,nextandmainstay green while a feature branch may be red.Status now names the 1.0.0 milestone in flight on
nextwith its milestone PR #190, and points at the tracker as the authoritative backlog rather than duplicating it. Next Step names a real open item, #152.Judgement calls:
DEBUGflag (#149), which landed but had no entry, and this change. Existing entries keep their bare#Nreferences untouched.make test-e2ein CI, cutting 1.0.0). Everything else there was already filed and is on the tracker.RULES.md"Build & Workflow" still says "Feature branches for all changes, merge to main when done", which the new Workflow contradicts.RULES.mdis owner-only and out of scope here; flagging it rather than editing it.Verification:
make fmtrun, no change toTODO.md(already Prettier-clean).make checkgreen on the rebased branch — 7 suites, 143 tests passed;prettier --check .: "All matched files use Prettier code style!" for bothlintandfmt-check. Rebased ontoorigin/nextate9fa8bebefore pushing; no conflicts.