Skip to content

Conversation

xitrox
Copy link

@xitrox xitrox commented Sep 19, 2025

Changes

  • Original change: git fetch --all fetches all remotes. The cheat sheet stated that it's fetching all branches.
  • Updated change: Remove the entry altogether since it's rarely used and therefore might not be well placed in a cheat sheet.

Context

A colleague of mine pointed out, that git fetch --all doesn't fetch all branches but all remotes.
git fetch --help confirms that.
After discussing in the PR I now suggest to remove it with an updated change.

@dscho dscho requested a review from jvns September 19, 2025 11:44
@jvns
Copy link
Collaborator

jvns commented Sep 19, 2025

Do you use git fetch --all a lot? I actually don't remember why I put that in there -- I don't think I've ever used it and obviously I don't really know what it does. It's hard for me to understand what the use case for "fetch all remotes" is. Unless you think it's important I'd be more inclined to remove it than fix it.

@xitrox
Copy link
Author

xitrox commented Sep 19, 2025

No absolutely not!

Some might claim that it helps keeping things updated if you're working on your own fork and an upstream repo.

As mentioned in the PR a colleague pointed out that it has the wrong description so I suggested a change. Taking the entry out entirely might however be a good option as well.

@jvns
Copy link
Collaborator

jvns commented Sep 19, 2025

Let's just remove it then; it's easy to put back if we ever decide it's important.

@xitrox xitrox changed the title Corrected the explanation for git fetch --all Removing git fetch --all Sep 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants