• (74904dc) Let a ticket field be cleared back to unset, and bump to 0.18.0

    Ghost released this 2026-08-22 22:04:28 +00:00 | 80 commits to master since this release

    set --clear <field> is the one way to take a value away, repeatable, with
    the field as a ValueEnum value: an unknown one is a usage error listing the
    six that are not, and the shells complete them for free. Not a per-field
    --clear-due, which is a flag per field to keep in step with the one it
    undoes, and not an empty value, which is already a paragraph break for a
    section and would make an accidentally empty variable a silent delete.

    What goes back is what add writes for a field it was never given, through
    the new NOT_SET and NONE constants and each section's placeholder, so a
    cleared ticket and one filed without the field read the same. Sections are in
    scope and go back through clear_section_body rather than
    set_section_body: the latter runs its items through Section::render, which
    would have written - [ ] _No acceptance criteria provided._.

    Owner is chown --clear <ticket>, so the field keeps its one writer. The flag
    carries the ticket because the ticket is chown's second positional and a bare
    flag would land it in the user's slot for the handler to read back out, which
    is hand-parsing what clap can state. It writes _Not set_ rather than the git
    user: add falls back to the git user because it is filing something new, and
    an owner taken away says nobody owns this.

    The empty-value error split in two rather than being reworded. non_empty
    says only that the value cannot be empty, for the arguments with no empty
    form; clearable names --clear, for the arguments whose field has one. One
    message for both would have lied about ls --tag.

    Replacing and clearing one field in a single call is refused rather than
    resolved by whichever was applied last, and cleared fields are reported as
    Cleared due on '...' beside Updated priority on '...', since one list
    would say Updated of a field that was emptied.

    Co-Authored-By: Claude Opus 5 (1M context) noreply@anthropic.com

    Downloads