issue/pr add-comment: read the comment from a file or stdin #17
skudr opened 3 weeks ago

Current behavior (tod 4.3.4). tod issue add-comment <ref> <content> and tod pr add-comment <ref> <content> take the comment only as an inline argument. Long Markdown – code fences, backticks, quotes, $ – breaks when it passes through a shell, and an agent has to escape it by hand. Passing - as the content posts a literal “-” comment instead of reading stdin.

Proposal. A --file <path> flag on both commands, where --file - reads stdin. The same would help --comment of issue change-state, pr discard and issue log-work.

Why. Agents post multi-paragraph reports with code blocks. Reading from a file removes the whole class of quoting failures.

1/1
Type
Enhancement
Priority
Normal
Assignee
Labels
No labels
Issue Votes (0)
Watchers (2)
Reference
TOD-17
Please wait...
Connection lost or session expired, reload to recover
Page is in error, reload to recover