feat(cli): support explicit GitHub repo target

[skulidropek]

Summary

• Add global --repo / PLAN_TO_GIT_REPO support for selecting the GitHub PR/comment target repository.
• Keep local state and history matching tied to the current checkout origin context.
• Pass the explicit target through hook, import, and sync flows, including gh pr view --repo and issue-comment API calls.
• Document the fork-origin workflow and add integration coverage.
• Split integration test helpers so CI file-size checks remain under the 1000-line invariant.

Proof of fix

• Причина: fork-origin environments need to push to a fork while posting plan comments to the upstream PR repository; previously plan-to-git used only origin as the GitHub API target.
• Решение: introduce an explicit target repo boundary via --repo / PLAN_TO_GIT_REPO, used only for GitHub PR/comment operations.
• Доказательство: integration test sync_explicit_pr_uses_explicit_repo_context captures local state under the origin repo key and posts to repos/upstream/repo/issues/17/comments when --repo upstream/repo is provided.

Validation

• cargo fmt --check
• cargo test
• cargo clippy --all-targets --all-features -- -D warnings
• rust-script scripts/check-file-size.rs

[skulidropek]

AI Session Backup

Commit: 3286a25
Status: success
Files: 5 (6.11 MB)
Links: README | Manifest

git status

On branch codex/explicit-repo-target
Your branch is up to date with 'origin/codex/explicit-repo-target'.

nothing to commit, working tree clean

[coderabbitai]

Warning

Review limit reached

@skulidropek, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 21 minutes and 6 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

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 credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate.

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, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 2254dd1a-5425-44d4-810b-3fc3162aeb2d

📥 Commits

Reviewing files that changed from the base of the PR and between 8e45db1 and debc5f5.

📒 Files selected for processing (10)

• README.md
• changelog.d/20260617_explicit_repo_context.md
• src/capture.rs
• src/git.rs
• src/github.rs
• src/main.rs
• src/normalize.rs
• tests/integration/cli.rs
• tests/integration/mod.rs
• tests/integration/support.rs

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/explicit-repo-target

---

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

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[skulidropek]

AI Session Backup

Commit: debc5f5
Status: success
Files: 5 (6.67 MB)
Links: README | Manifest

git status

On branch codex/explicit-repo-target
Your branch is up to date with 'origin/codex/explicit-repo-target'.

nothing to commit, working tree clean