sneak
135fd9edc1
check / check (push) Successful in 2m39s
The workflow lines now say who merges where: clawbot squash-merges reviewed issue PRs into next, only sneak merges next into main, and a deploy is a squash commit from main onto prod, never automatic. Status lists what is on next today, each item linked to its issue: the repo standards, interface detection on Linux and macOS, the macOS VPN detection fix, the Starlink status lines, the version stamp, and CI running script/cibuild. Next Step is the owner's merge of the milestone PR and a first run on a real Mac. Model: opus-5-5
1.8 KiB
1.8 KiB
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 frommain) - do the work; open a PR based on
next(never onmain) - pass an independent review, then
clawbotsquash-merges it intonext - 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.
Status
On next:
- Repo standards (#1): the
script/entrypoints, the vendored.golangci.yml, andREPO_POLICIES.md. - Interface detection on Linux and macOS (#2).
- The fix for macOS VPN detection (#8).
- Starlink status lines (#3).
- A version stamp: built with
make buildor a plaindocker build ., the binary logs its git tag or short commit at startup (#10). - CI that runs
script/cibuildon every push to a branch (#12).