Skip to content

feat(pr): Resolve current branch PR for merge, close, and comment - #5

Open
euxaristia wants to merge 1 commit into
mainfrom
feat/implicit-pr-context-mutations
Open

feat(pr): Resolve current branch PR for merge, close, and comment#5
euxaristia wants to merge 1 commit into
mainfrom
feat/implicit-pr-context-mutations

Conversation

@euxaristia

Copy link
Copy Markdown
Owner

Summary

gt pr view already resolves 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 added for view inconsistent across the pr subcommands. Running gt pr merge on a checked-out feature branch now works the same way gt pr view does.

Changes

internal/cmd/pr.go

  • Add resolvePRNumber, which uses an explicit argument when present and otherwise looks up the open PR for the current branch via the existing findPRForBranch.
  • merge, close, and comment now accept an optional number (cobra.MaximumNArgs(1)) and resolve the repo/token before looking up the branch PR.

Test plan

  • go build ./... clean
  • go test ./internal/cmd/ -run TestPR 27/27 pass

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.
@coderabbitai

coderabbitai Bot commented Jul 15, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@euxaristia, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 57 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 0a9d3048-8f05-4bb5-9f20-b3613fb50c56

📥 Commits

Reviewing files that changed from the base of the PR and between d880cc3 and 0b2cba2.

📒 Files selected for processing (1)
  • internal/cmd/pr.go

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant