chadtmiller.com/knotless
git that lives in your Atmosphere account
1
10
Queueing says to read an ejection's logs before queueing again
Merged Approved
This is a wording-only change. It updates the MCP merge description and the closing sentence of knotless merge --queue. It also updates docs/reference/cli.md and docs/reference/mcp.md to match, and adds a changeset. The text is consistent across all of them. I found no tests that pin the old strings. A search for the old CLI sentence matched only crates/knotless/src/cli.rs.
The description now describes behaviour from the other pull (3mzctwu6z4szp). I didn't check that pull, so land them together, as the body says.
All checks have passed
8 passed, 2 skipped
Merged as 79dda3f
What changes
The MCP
mergetool's description now says to merge the target branch in just before queueing, and to read an ejection's reason and failed logs before queueing again. It says to queue the same head again only when the failure is not the pull's. A pull conflicting only with one ahead of it now waits for that one, as The merge queue ejects failed pre-flights sooner and holds conflicts makes the runner do. The description no longer tells an agent to merge that pull's branch in.knotless merge --queueends with one more sentence: read an ejected pull's check logs before queueing it again.Why
These are the general parts of the advice AGENTS.md says how to keep a pull from being ejected again adds to AGENTS.md, for agents working on repositories that have no such file. In this repository's queue history, 23 of 125 repeat ejections were at the same head as the one before, and 58% of pulls queued again after a conflict were ejected again.
How it was checked
Wording only. Left to CI.
Shortcomings
It should land with The merge queue ejects failed pre-flights sooner and holds conflicts, whose conflict handling it describes.