-
(9688d34) Add tags set, and bump to 0.26.0
released this
2026-08-23 14:09:03 +00:00 | 63 commits to master since this releaseA tag declared with the wrong annotation was stuck with it, which is 32e98ab's
hole arriving before the writer rather than after. The campaigns entry on this
board was already in that state: it reserved the singular for the campaign
command, and stopped being true the moment that tag was rolled in.worklane tags set <tag> --annotationreplaces the whole annotation.
--annotationis required, so a bare call is a usage error rather than a
silent no-op, and an empty one writes the placeholder, which is why there is
no--clear.addandsetrefuse what the other is for, each naming the
other, so which one wrote a line is never a question of which was typed.No
--force: a codename is guarded because a campaign is addressed by it,
where an annotation is prose written to be revised. No rename: the tag is the
key, so changing it means rewriting the Tags field of every ticket carrying
it.reportgrewreport_in, which takes the colour.reportpaints its subject
green and green means title, so a tag could not reuse it: a tag is drawn in a
TAG_COLORSslot or it is drawn wrong. Same wording, decision passed in,
which is the tradepaintmakes withcolor_text.The no-op compares the rendered file rather than the annotation, the way
applycompares content for a ticket field.tags settakes a tag the board already has, so it joins the new
TAG_NESTED_COMMANDSand gets a fish rule offeringworklane tags;tags addstays ruleless inTAG_NEW_COMMANDS. The guard now names both lists, so
the next tag positional has to pick one.Co-Authored-By: Claude Opus 5 (1M context) noreply@anthropic.com
Downloads