Skip to content

Conversation

heartacker
Copy link
Contributor

  • Add a new property to enable fetching all remotes by default.
  • Refactor fetch logic to use repository settings directly instead of local properties.

@love-linger
Copy link
Collaborator

If you want to just fetch specific remote, you should use context menu entry of selected remote:
image

@love-linger love-linger self-assigned this Aug 4, 2025
@love-linger love-linger added the not-planned It's not planned in the future label Aug 4, 2025
@heartacker
Copy link
Contributor Author

If we're simply discussing the  git fetch  function, along with its corresponding button and shortcut key, I think what we should focus on is its pure original meaning. Its behavior should be as simple as just entering  git fetch  in the terminal. Frankly speaking, I don't think  all  should be set as the default option.

Although we can start from the  remote  side and only  fetch  a specific  remote , it's really not that fast. I just want  git fetch  and its original behavior, and have a shortcut key for it.

@heartacker
Copy link
Contributor Author

The  fetch  button and its shortcut key should follow its original behavior. It should  fetch  the default remote. And that's exactly what we want. Why does it have to be  fetch all  and set as the default permanently? It should rather cover the basic and original meaning. Moreover, after using  fetch all , there may be inconveniences in some scenarios, such as the need for password verification.

If there is an option, I think  all  should be disabled,by default

- Add a new property to enable fetching all remotes by default.
- Refactor fetch logic to use repository settings directly instead of local properties.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
not-planned It's not planned in the future
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants