diff options
| author | Craig Jennings <c@cjennings.net> | 2026-05-26 20:10:42 -0500 |
|---|---|---|
| committer | Craig Jennings <c@cjennings.net> | 2026-05-26 20:10:42 -0500 |
| commit | cfc42c41426d61f53c49b1f192751bcd061e57ae (patch) | |
| tree | 0091739c4f499c5a6a849f6241139479a23f14f0 /docs/issue-query-spec.org | |
| parent | 34c67ddc3b72f92033ced3f86346f3483f5ba463 (diff) | |
| download | pearl-cfc42c41426d61f53c49b1f192751bcd061e57ae.tar.gz pearl-cfc42c41426d61f53c49b1f192751bcd061e57ae.zip | |
fix(commands): run add-comment and delete from anywhere in a ticket
pearl-add-comment and pearl-delete-current-issue guarded position with the nearest-heading check, so from inside a comment subtree, or any heading without a LINEAR-ID, they errored "Not on a Linear issue heading". Both docstrings already claimed they work from anywhere in the subtree, so the behavior was just wrong.
The edit and save commands already climb to the issue via pearl--goto-issue-heading-or-error. I switched these two to the same guard, so every ticket-scoped command resolves the enclosing issue from anywhere in its subtree, including from inside a comment. The redundant LINEAR-ID re-checks are gone since the guard guarantees it. Walk-up tests added for both.
Diffstat (limited to 'docs/issue-query-spec.org')
0 files changed, 0 insertions, 0 deletions