feat(pr): Resolve current branch PR for merge, close, and comment - #5
feat(pr): Resolve current branch PR for merge, close, and comment#5euxaristia wants to merge 1 commit into
Conversation
pr view already falls back to the open PR for the current branch when no number is given, but merge, close, and comment still required an explicit number. This makes the implicit PR context inconsistent across the pr subcommands. Add a shared resolvePRNumber helper that uses an explicit argument when present and otherwise looks up the open PR for the current branch, and wire it into merge, close, and comment.
|
Warning Review limit reached
Next review available in: 57 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Summary
gt pr viewalready resolves the open PR for the current branch when no number is given, butmerge,close, andcommentstill required an explicit number. This makes the implicit PR context added forviewinconsistent across theprsubcommands. Runninggt pr mergeon a checked-out feature branch now works the same waygt pr viewdoes.Changes
internal/cmd/pr.goresolvePRNumber, which uses an explicit argument when present and otherwise looks up the open PR for the current branch via the existingfindPRForBranch.merge,close, andcommentnow accept an optional number (cobra.MaximumNArgs(1)) and resolve the repo/token before looking up the branch PR.Test plan
go build ./...cleango test ./internal/cmd/ -run TestPR27/27 pass