Fetch checkpoint refs by URL to avoid polluting origin config#934
Merged
Conversation
git fetch --filter=blob:none <remote-name> persists remote.<name>.promisor=true and remote.<name>.partialclonefilter=blob:none into .git/config. Since #712, the four fetch helpers in git_operations.go passed "origin" as a named remote, which turned users' origin into a promisor remote repo-wide — affecting future `git fetch origin` / `git pull` and not just checkpoint reads. Resolve origin's URL first and pass the URL as both CheckpointGitCommand target and the remote argument. Anonymous URL fetches do not touch remote.*.promisor / remote.*.partialclonefilter in local config. Adds a regression test that fails against the pre-fix code and passes after. Does not yet unstick the config on users who already ran the affected CLI — that cleanup is a follow-up. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> Entire-Checkpoint: 4e0f55d5b407
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the metadata/v2 fetch helpers to fetch checkpoint-related refs by explicit origin URL (instead of the origin remote name) to prevent git fetch --filter=... from persisting partial-clone settings into remote.origin.* in .git/config.
Changes:
- Add
strategy.OriginURL()helper to resolve the configured origin fetch URL. - Update multiple
git fetch --filter=blob:nonecode paths to fetch by URL rather than remote name. - Add a regression test asserting these fetch helpers do not set
remote.origin.promisor/remote.origin.partialclonefilter.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 4 comments.
| File | Description |
|---|---|
cmd/entire/cli/strategy/checkpoint_remote.go |
Exposes OriginURL() to retrieve the origin remote URL for URL-based fetches. |
cmd/entire/cli/git_operations.go |
Switches several partial-clone fetch commands to use origin URL to avoid config pollution. |
cmd/entire/cli/fetch_no_config_pollution_test.go |
Adds regression coverage to ensure origin config is not modified by these fetches. |
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Comment @cursor review or bugbot run to trigger another review on this PR
Reviewed by Cursor Bugbot for commit d958ed4. Configure here.
pjbgf
reviewed
Apr 13, 2026
Entire-Checkpoint: b4907926d56e
Entire-Checkpoint: ca3b4b514c9a
Entire-Checkpoint: bcc1f13611d9
Entire-Checkpoint: 4c57ebbd5ca6
pjbgf
approved these changes
Apr 13, 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.

This does three things:
entire/checkpoints/v1branches.git/configsetting is only created for the url not the remote in general impacting all branches.git/configand only allow expected changes.Note:
Running 0.5.4 introduced fetches which will cause a change in the
.git/configlike:This was an unintentional result of the changes when fetching