chadtmiller.com/knotless
git that lives in your Atmosphere account
1
10
AGENTS.md says how to keep a pull from being ejected again
AGENTS.md+15−4
| @@ -310,16 +310,27 @@ build, fails a test or misses a line never fails a batch. A pass against | ||
an older `main` counts. Pulls queued behind it that are ready go ahead | ||
meanwhile, and `knotless queue` says `pre-flight check` or `pre-flight | ||
test` while it waits. Queueing turns away a pull that conflicts with `main` or whose | ||
checks failed, saying why. One ejected: read why with `knotless show`, | ||
fix it, and queue it again; one that conflicts with a pull ahead of it | ||
can take that pull's branch merged in, or wait for it to land and take | ||
`main`. Ejected three times for the same reason, stop and say so rather | ||
checks failed, saying why, so merge `main` into the branch just before | ||
queueing. One ejected: read why with `knotless show`, and the failed | ||
check's log, then fix it and queue it again. Queue the same head again | ||
only when the log shows the failure is not the pull's, such as a test or | ||
a line it does not touch that fails other pulls too, and then fix or | ||
quarantine what failed rather than leave it for the next pull. A pull | ||
that conflicts with one queued ahead of it waits for that one to land or | ||
leave; ejected then, it conflicts with `main`, so merge `main` into it. | ||
Ejected three times for the same reason, stop and say so rather | ||
than queue it again. When several agents land pulls at once, one of them | ||
lands them all, and the rest hand it their pulls' URIs rather than each | ||
watching its own. A deploy restarts the runner. A batch whose checks | ||
pass while it stops still lands; one it cuts off is built and checked | ||
again, with nothing to do. | ||
| ||
Most conflicts are in the docs pages nearly every change updates, | ||
`docs/design/serve.md` and `docs/reference/api.md` above all: add to | ||
them where the change belongs, and leave the lines around it as they | ||
are. Agents working at once take different parts of the code, and of | ||
those pages, where they can. | ||
| ||
Work that should not reach `main` yet goes on a feature branch, | ||
`feature/<name>`, cut from `main`. Its parts are pulls into it, made as | ||
pulls into `main` are but with `feature/<name>` as the base: the seven | ||