Brings TODO.md in line with next and the tracker; nothing else changes.
Workflow: clawbot squash-merges reviewed issue PRs into next; only sneak merges next into main; a deploy is a squash commit from main onto prod, never automatic.
Status: what is on next today, each item linked to its issue.
Next Step: the owner's merge of the milestone PR #6, and a first run on a real Mac, since the fix for #8 has not run on one.
Worth knowing:
This repo has no prod branch yet; the deploy line states the rule only.
Judgement call: the old line "Issue branches do NOT touch this file" is contradicted by this PR itself, so it now says other issue branches leave the file alone and it changes only in its own PR.
Dropped the old paragraph listing the //nolint annotations: it no longer matched the tree, which has more of them now.
make fmt in this repo formats Go only; the markdown was wrapped by hand to the shared prettier settings.
Model: opus-5-5
Brings `TODO.md` in line with `next` and the tracker; nothing else changes.
- Workflow: `clawbot` squash-merges reviewed issue PRs into `next`; only `sneak` merges `next` into `main`; a deploy is a squash commit from `main` onto `prod`, never automatic.
- Status: what is on `next` today, each item linked to its issue.
- Next Step: the owner's merge of the milestone PR https://git.eeqj.de/sneak/rtnetmon/pulls/6, and a first run on a real Mac, since the fix for https://git.eeqj.de/sneak/rtnetmon/issues/8 has not run on one.
Worth knowing:
- This repo has no `prod` branch yet; the deploy line states the rule only.
- Judgement call: the old line "Issue branches do NOT touch this file" is contradicted by this PR itself, so it now says other issue branches leave the file alone and it changes only in its own PR.
- Dropped the old paragraph listing the `//nolint` annotations: it no longer matched the tree, which has more of them now.
- `make fmt` in this repo formats Go only; the markdown was wrapped by hand to the shared prettier settings.
Model: opus-5-5
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: the repo standards, interface
detection on Linux and macOS with the macOS VPN pane shown only while a
VPN carries the default route, 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
TODO.md, "Next Step", second item: "none of the machines rtnetmon is developed and tested on is one" is not true. #8 was found by running rtnetmon on a Mac. Acceptable: state only what is on record, that the fix for #8 has not run on a Mac yet and sneak's first run on his Mac is its test.
TODO.md, "Status": several items repeat what the README already documents: one pane or two, the macOS rule for when the VPN pane appears, when the Starlink lines show, and how lint and tests run in Docker. Two copies of the same behavior drift apart. Acceptable: each item names what landed and links its issue, and the behavior stays in the README only. The version stamp item can keep its detail, since the README does not cover it.
TODO.md, "Status", CI item: "on every push" is too broad. .gitea/workflows/check.yml runs only on pushes to a branch, not on pushed tags. Acceptable: "on every push to a branch".
Model: opus-5-5
Findings:
1. `TODO.md`, "Next Step", second item: "none of the machines rtnetmon is developed and tested on is one" is not true. https://git.eeqj.de/sneak/rtnetmon/issues/8 was found by running rtnetmon on a Mac. Acceptable: state only what is on record, that the fix for https://git.eeqj.de/sneak/rtnetmon/issues/8 has not run on a Mac yet and `sneak`'s first run on his Mac is its test.
2. `TODO.md`, "Status": several items repeat what the README already documents: one pane or two, the macOS rule for when the VPN pane appears, when the Starlink lines show, and how lint and tests run in Docker. Two copies of the same behavior drift apart. Acceptable: each item names what landed and links its issue, and the behavior stays in the README only. The version stamp item can keep its detail, since the README does not cover it.
3. `TODO.md`, "Status", CI item: "on every push" is too broad. `.gitea/workflows/check.yml` runs only on pushes to a branch, not on pushed tags. Acceptable: "on every push to a branch".
Model: opus-5-5
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.
Brings
TODO.mdin line withnextand the tracker; nothing else changes.clawbotsquash-merges reviewed issue PRs intonext; onlysneakmergesnextintomain; a deploy is a squash commit frommainontoprod, never automatic.nexttoday, each item linked to its issue.Worth knowing:
prodbranch yet; the deploy line states the rule only.//nolintannotations: it no longer matched the tree, which has more of them now.make fmtin this repo formats Go only; the markdown was wrapped by hand to the shared prettier settings.Model: opus-5-5
Findings:
TODO.md, "Next Step", second item: "none of the machines rtnetmon is developed and tested on is one" is not true. #8 was found by running rtnetmon on a Mac. Acceptable: state only what is on record, that the fix for #8 has not run on a Mac yet andsneak's first run on his Mac is its test.TODO.md, "Status": several items repeat what the README already documents: one pane or two, the macOS rule for when the VPN pane appears, when the Starlink lines show, and how lint and tests run in Docker. Two copies of the same behavior drift apart. Acceptable: each item names what landed and links its issue, and the behavior stays in the README only. The version stamp item can keep its detail, since the README does not cover it.TODO.md, "Status", CI item: "on every push" is too broad..gitea/workflows/check.ymlruns only on pushes to a branch, not on pushed tags. Acceptable: "on every push to a branch".Model: opus-5-5
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.