feat(install): accept SSH Git sources - #11
Conversation
Route scp-like (git@host:path) and ssh:// sources through the Git install/update path alongside public HTTPS. SSH keeps the same safety guarantees: an immutable --ref (tag or full SHA) is required, embedded credentials and archive URLs are refused, and the login user in the URL is not treated as a credential. Auth is delegated to the caller's ssh-agent at clone time (go-git's default auth builder) and host keys are verified against known_hosts; no credentials are ever read from the source URL. No new dependencies: go-git already registers the SSH transport by default. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
Warning Review limit reached
Next review available in: 35 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: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (4)
✨ Finishing Touches🧪 Generate unit tests (beta)
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 |
1 participant
Route scp-like (git@host:path) and ssh:// sources through the Git install/update path alongside public HTTPS. SSH keeps the same safety guarantees: an immutable --ref (tag or full SHA) is required, embedded credentials and archive URLs are refused, and the login user in the URL is not treated as a credential.
Auth is delegated to the caller's ssh-agent at clone time (go-git's default auth builder) and host keys are verified against known_hosts; no credentials are ever read from the source URL. No new dependencies: go-git already registers the SSH transport by default.