Parent PRD
#1
What to build
Enhance the existing bb pr list command with an --author / -A flag that filters pull requests by author nickname. When the value @me is passed, resolve it to the authenticated user's nickname via GET /user.
End-to-end: the user runs bb pr list --author zoldyzdk or bb pr list --author @me and sees only PRs from that author. Running bb pr list without --author continues to show all PRs (preserving existing behavior).
This requires:
- Enhancing
ListPullRequests in the API layer to accept a Bitbucket query string parameter (q=author.nickname="<value>")
- Adding the
--author flag to the pr list Cobra command
- Resolving
@me to the current user's nickname using the existing GetCurrentUser() API call
Acceptance criteria
Blocked by
None - can start immediately
User stories addressed
- User story 21
- User story 22
- User story 23
Parent PRD
#1
What to build
Enhance the existing
bb pr listcommand with an--author/-Aflag that filters pull requests by author nickname. When the value@meis passed, resolve it to the authenticated user's nickname viaGET /user.End-to-end: the user runs
bb pr list --author zoldyzdkorbb pr list --author @meand sees only PRs from that author. Runningbb pr listwithout--authorcontinues to show all PRs (preserving existing behavior).This requires:
ListPullRequestsin the API layer to accept a Bitbucket query string parameter (q=author.nickname="<value>")--authorflag to thepr listCobra command@meto the current user's nickname using the existingGetCurrentUser()API callAcceptance criteria
bb pr list --author <nickname>returns only PRs authored by that userbb pr list --author @meresolves to the authenticated user's nickname and filters accordinglybb pr list(without--author) continues to show all PRs (no behavior change)--authorflag works in combination with existing--stateand--limitflags@meis used but the user is not authenticatedBlocked by
None - can start immediately
User stories addressed