feat(comments): add unresolve CLI subcommand to reopen threads - #8
Open
Millon15 wants to merge 1 commit into
Open
feat(comments): add unresolve CLI subcommand to reopen threads#8Millon15 wants to merge 1 commit into
unresolve CLI subcommand to reopen threads#8Millon15 wants to merge 1 commit into
Conversation
The bitbucket client (UnresolvePRComment) and the MCP `unresolve` action
already reopen a resolved thread, but the CLI had no matching subcommand —
users could resolve a thread from the terminal yet had to switch to the
browser to reopen one.
Wire `bbkt prs comments unresolve <pr-id> <comment-id>`, mirroring resolve
(DELETE on the resolve sub-resource). Update the README and CLI reference.
Adds tests asserting the client DELETEs .../comments/{id}/resolve and
validates its required fields.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds a
bbkt prs comments unresolve <pr-id> <comment-id>CLI subcommand to reopen a resolved review thread.Why
The terminal could already resolve a thread (
prs comments resolve), and both the bitbucket client (UnresolvePRComment) and the MCPunresolveaction already reopen one — but the CLI had no matching subcommand. A CLI user who resolved a thread had to switch to the browser to reopen it. This closes that asymmetry.How
prCommentsUnresolveCmd, mirroringresolveexactly (same arg shape[workspace] [repo-slug] <pr-id> <comment-id>, sameParseArgs/validation), calling the existingclient.UnresolvePRComment(DELETE on the…/comments/{id}/resolvesub-resource).prs comments; added to the command-group examples andShort.unresolve.No new client/MCP code — this is purely the missing CLI surface over functionality that already shipped.
Tests
TestUnresolvePRComment_SendsDelete— asserts the client issuesDELETE …/comments/99/resolve.TestUnresolvePRComment_ValidatesRequiredFields— table test over the four missing-field cases.Notes
Branches off
mainand is independent of the other open PRs (resolve{}-body fix, list-resolution,--all) — no shared functions, merges in any order.