check / check (push) Successful in 2m16s
Removes the Status section, which listed work already landed on next, and the Next Step section, whose two items are done: the milestone PR merged and the binary has run on a Mac. The Workflow section stays. Model: opus-5-5
18 lines
801 B
Markdown
18 lines
801 B
Markdown
# Workflow
|
|
|
|
One issue per unit of work, one branch and one PR per issue:
|
|
|
|
- ensure a tracked issue exists with a definition of done
|
|
- branch from `next` (never from `main`)
|
|
- do the work; open a PR based on `next` (never on `main`)
|
|
- pass an independent review, then `clawbot` squash-merges it into `next`
|
|
- push; nothing stays local-only
|
|
|
|
`next` is the branch for the next milestone and must stay green and mergeable to
|
|
`main` without notice. Only `sneak` merges `next` into `main`. No commits land
|
|
directly on `main` or `next`, only merges via PRs. A deploy is a squash commit
|
|
from `main` onto `prod`; `prod` never follows `main` automatically.
|
|
|
|
Other issue branches do not touch this file; it changes only in its own PR to
|
|
`next`, because every branch editing `TODO.md` conflicts with every other.
|