feat(comments): expose thread resolution in list output (CLI + MCP) - #6
Open
Millon15 wants to merge 1 commit into
Open
feat(comments): expose thread resolution in list output (CLI + MCP)#6Millon15 wants to merge 1 commit into
Millon15 wants to merge 1 commit into
Conversation
Bitbucket's default PR-comments projection omits the resolution object, so callers cannot tell an open thread from a resolved one. Request it with fields=+values.resolution.user.display_name, add a Resolution field to PRComment, and surface a Resolved column in the CLI table. The MCP list tool returns the same struct, so it gains resolution for free. Fixture + test cover resolved (non-nil), explicit-null, and absent cases.
Millon15
added a commit
to Millon15/bbkt
that referenced
this pull request
Jun 25, 2026
…-snell#6 x zach-snell#7 integration) Combining the resolution-aware list (zach-snell#6) with --all paging (zach-snell#7): ListAllPRComments routes every page through ListPRComments, which appends `&fields=%2Bvalues.resolution.user.display_name`. The list_comments_paged cassette was recorded before zach-snell#6, so its request URLs lacked that param and the exact-URL VCR matcher (matchMethodAndURL) missed. Add the param to both recorded request URLs. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.
Problem
Bitbucket's default PR-comments projection omits the thread
resolutionobject, sobbkt prs comments list(and the MCP list tool) cannot distinguish an open thread from a resolved one.Fix
fields=+values.resolution.user.display_nameto the list URL (+percent-encoded as%2B, kept out of the format string sofmtdoes not treat it as a verb).Resolutionfield (+Resolutiontype) toPRComment.Resolvedcolumn in the CLI table (shows the resolver). The MCP list tool returns the same struct, so it gains resolution for free.Verification
TestFixture_Comments_ResolutionParsescovers resolved (non-nil + resolver), explicit-null, and absent cases via a VCR cassette.go test ./...green; verified live against a real PR (correct resolved-vs-open split + resolver name).