You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Committed flight record fails markdownlint MD013 when the quoted ask has long lines #544
A visual flight whose record home is the committed file can't land in a repo whose markdownlint limits code-block line length, because the record quotes the ask and grounds verbatim inside a fenced block.
What happened (0.49.0): the adopter repo sets MD013 with code_block_line_length: 200. The tower's ask file had paragraphs written as single lines (240, 250 and 362 characters). flight-record.sh land exited 4 when the repo's pre-commit format hook rejected the record. The worker is correctly barred from editing the operator's quoted text, so it parked, and the only unblocks it could offer were changing repo lint config, --no-verify (which just moves the failure to CI, since the same repo runs markdownlint in CI), or skipping the record.
Why it matters: any flight whose ask has a long line fails at the very last step, after convergence is done, and the failure isn't visible at dispatch time.
Possible directions
Have flight-dispatch.sh dispatch (or the tower when writing the ask file) check the ask/grounds against the line length the record will be linted at, and warn or reflow before placing the flight.
Render the quoted ask in a form MD013 doesn't apply to by default (a blockquote, which wraps), or emit a scoped <!-- markdownlint-disable MD013 --> around the quote.
Document that specs/_flights/** may need an MD013 exemption in repos with code-block limits.
Related: the worker's prompt showed a ghost-text suggestion "use --no-verify for this one record" while parked on this, which is the ghost-text concern in #341.
Activity