2bab52dc71
The echo body wrote `no longer blocked by #9` unbackticked, twice in one sentence. GitHub linkifies both, so every echo posted a pair of "mentioned in" events onto this repo's issue #9 — an issue with nothing to do with the one being echoed. On a 15-minute cron that is one pair per `blocked` issue on the board, and the first sweep after merge would have written the whole board's worth at once. The file's own convention two branches down already avoids this: the `blocked-unparseable` comment code-spans its `Blocked by #N` for exactly this reason. The prose is unchanged, the rendered set is unchanged, and the marker digests the parsed set rather than the comment body, so no marker moves. |
||
|---|---|---|
| .. | ||
| changelog-armed | ||
| changelog-assembled | ||
| changelog-monotonic | ||
| docs-sync | ||
| drill-recorded | ||
| issueflow-reconcile | ||
| labels-reconcile | ||
| labels-scope | ||
| runner-isolated | ||
| .gitkeep | ||