• (9688d34) Add tags set, and bump to 0.26.0

    Ghost released this 2026-08-23 14:09:03 +00:00 | 63 commits to master since this release

    A 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> --annotation replaces the whole annotation.
    --annotation is 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. add and set refuse 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.

    report grew report_in, which takes the colour. report paints its subject
    green and green means title, so a tag could not reuse it: a tag is drawn in a
    TAG_COLORS slot or it is drawn wrong. Same wording, decision passed in,
    which is the trade paint makes with color_text.

    The no-op compares the rendered file rather than the annotation, the way
    apply compares content for a ticket field.

    tags set takes a tag the board already has, so it joins the new
    TAG_NESTED_COMMANDS and gets a fish rule offering worklane tags; tags add stays ruleless in TAG_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