Make Fetch and Pull separate buttons

Comments: 5

• 21 Oct, '22
  Roland

  It would be nice if the fetch all and the pull features would be on a seperate button on the toolbar.

  Like
• 27 Oct, '22
  bekkra

  Alternatively, you could add just "Fetch" to "Fetch all" in the drop-down menu. Rationale: "pull" makes more sense on the command line. We have the luxury of the GUI here, so allow us the freedom of choice :)

  Like
• 08 Feb, '23
  Kornelije

  I would also say that given that the dropdown next to Pull already contains Fetch All and 3 variants of Pull, I think the dropdown menu should be open automatically on hover, instead of on arrow click. That way, both pull (as a default big button) and all other actions could be done with a single click.
  
  It's a nitpick, I know, but the UX would be so gooooood :)

  Like
• 29 Mar, '23
  Jonas Ahrentorp

  I think that separating "Fetch All" to a separate button would be a good thing. It's a bit weird to have functionality that affects all branches together with functionality that only affects the current branch. Even though I read "All" in "Fetch All" I at first thought that it only fetches the current branch since everything else connected to the button says "Pull" and pull only affects the current branch.

  Like
• 13 Jan
  John Doe

  I would like a dedicated Fetch All button as well.
  
  Fetch all is a safe action to check what the status is of all remotes. Hiding it behind the Pull dropdown disincentivises fetching, which is bad, more fetching is a good habit to get people into.
  
  There's plenty of horizontal space in the bar, and if people are against the bar growing, it could be an option.

  Like