Conversation
The Source Control switch showed Git as enabled and could not be changed, so slow repositories kept running status, fetch, and checkpoints. The switch now writes enableVersionControl, and Git work stops while it is off. Turning it back on publishes a full status snapshot.
Owner
Author
|
Opened upstream. |
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.
What Changed
Settings → Source Control → Version control can turn Git off for an environment or one project. While it is off, detection, status, fetch, auto-pull, and checkpoints do not run Git. Turning it back on reloads local and remote status and publishes a full snapshot to open streams.
Why
The Git row showed enabled and the control could not be changed, so huge or slow repositories (including git-svn) kept paying for Git work. The switch now writes
enableVersionControl. Existing settings stay on.A missing project-root lookup stays off when any opt-out exists, so a failed lookup cannot fall through to the enabled environment default. Queued Git work rechecks the switch inside the remote write lock. A zero fetch interval still checks the switch, so an open stream drops its cached repository status instead of emitting it forever.
pingdotgg#13595
UI Changes
Web and desktop Settings → Source Control: the Git switch is writable, including a mixed state when selected projects disagree. Mobile Source Control has the same switch. Jujutsu stays a read-only availability indicator.
Checklist
Grok 4.7, Cursor cloud agent