feat(code reviewer) use blobless clone for github and gitlab - #4847
Merged
Conversation
Contributor
Code Review SummaryStatus: No Issues Found | Recommendation: Merge Executive SummaryThe blobless-clone allow-list is now scoped to GitHub/GitLab only, and a filter-rejection retry (with a covering test) resolves the previously flagged fallback gap. Files Reviewed (2 files)
Previous Review Summary (commit 213d6ea)Current summary above is authoritative. Previous snapshots are kept for context only. Previous review (commit 213d6ea)Status: 1 Issue Found | Recommendation: Address before merge Executive SummaryThe blobless partial-clone optimization for GitHub/GitLab code review sessions removes the earlier fallback-on-failure logic without a test covering remotes that reject unsupported object filters. Overview
Issue Details (click to expand)WARNING
Files Reviewed (2 files)
Reviewed by claude-sonnet-5 · Input: 20 · Output: 3.6K · Cached: 396.4K Review guidance: REVIEW.md from base branch |
… add filter fallback
jeanduplessis
approved these changes
Jul 28, 2026
This was referenced Jul 29, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Cloud code review sessions now use a blobless partial clone (
git clone --filter=blob:none) for GitHub and GitLab repositories, instead of a full clone. This keeps the initial clone bounded by the current working tree rather than full repository history, avoiding clone timeouts on large repos, while still fetching the full commit graph so incremental diffs and merge-base checks keep working (blobs are fetched lazily on demand).Bitbucket review sessions, and any other/unrecognized
gitremote, keep a normal full clone.Changes
isCodeReviewSession,isBitbucketReviewSession, andisBloblessReviewCloneEligiblehelpers insession-bootstrap.tsto gate the clone strategy by session platform and repo provider.cloneRepositorynow clones with--filter=blob:noneonly for GitHub/GitLab code review sessions; if the server rejects the filter outright (rather than silently ignoring it), it retries once with a normal full clone so a review is never lost to the optimization.sanitizeBitbucketCodeReviewRemotenow reusesisBitbucketReviewSessioninstead of duplicating the same platform check inline.Verification
Visual Changes
N/A
Reviewer Notes
Bitbucket keeps a full clone as a deliberate tradeoff: enabling the blobless clone there would require adding outbound credential injection for Bitbucket to the sandbox's outbound proxy, which today only supports GitHub and GitLab. That's out of scope for this change.