Repository navigation
Conversation
love-linger
reviewed
Oct 8, 2026
| get; | ||
| set; | ||
| } = false; | ||
| } = true; |
Collaborator
There was a problem hiding this comment.
I do not want to change this option. Not all users like this feature because when auto-fetch happends, it may interfere with the work that the user is carrying out.
This branch has not been deployed
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.
Problem
Auto-fetch is off by default. A repository therefore keeps showing stale remote state: branches look up to date and pushable while the remote has moved on, and the user only finds out after fetching by hand.
Change
EnableAutoFetchdefaults totrue.Existing users keep whatever they saved in
preference.json; only new configurations change. The option can still be turned off in Preferences > Git, and remotes withdisableAutoFetchare still skipped.