Description
bkt pr comments currently shows only ID, author, and truncated text. This PR adds:
- File path and line number for inline comments
- Resolved status for comment threads
- Task vs Comment distinction (severity BLOCKER = task)
- Task completion status
- Nested reply threads (replies are silently dropped)
Proposed solution
- Add
--details flag for verbose multi-line output per comment
- Distinguish "Comment" vs "Task" in the header
- Use "Resolved: yes" for comment threads, "Complete: yes/no" for tasks (matching Bitbucket's own terminology)
- Flatten nested comment replies with depth-based indentation
- Show indented replies in default (non-details) mode too
Depends on #107 (activities endpoint fix).
Note: overlap between pr comments and pr task
bkt pr task list returns 404 on some DC instances — the /tasks endpoint doesn't exist there. Tasks are only surfaced as comments with severity: "BLOCKER" via the /activities endpoint.
This creates some overlap between pr comments --details and pr task list, since both can show tasks. However, pr comments --details serves a different use case: seeing all open items (comments and tasks) in one view, which is what a reviewee typically needs when working through a PR.
Description
bkt pr commentscurrently shows only ID, author, and truncated text. This PR adds:Proposed solution
--detailsflag for verbose multi-line output per commentDepends on #107 (activities endpoint fix).
Note: overlap between
pr commentsandpr taskbkt pr task listreturns 404 on some DC instances — the/tasksendpoint doesn't exist there. Tasks are only surfaced as comments withseverity: "BLOCKER"via the/activitiesendpoint.This creates some overlap between
pr comments --detailsandpr task list, since both can show tasks. However,pr comments --detailsserves a different use case: seeing all open items (comments and tasks) in one view, which is what a reviewee typically needs when working through a PR.