Separate git's pull and push buttons

[alikazemkhanloo]

Scope: git Feature: separate pull and push buttons to have more control over git commands and be less prone to unwanted pull/push.

Scenario: I always use git synchronize button to push my changes. I rebased a (really long) branch and pushed it to the origin. later on, a colleague, using vscode's sync button, pull&merge&pushed that branch. Now we have duplicate commits on origin. And later, I pulled his merge commit and pushed my new changes to origin (using sync button). after a week I realized the history of git is messed up.

Thanks.

[vscodenpa]

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.

Happy Coding!

[vscodenpa]

This feature request has not yet received the 20 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.

Happy Coding!

[Tyler-2]

This is the main thing that keeps me from happily switching to VSCodium.

I don't want to accidentally push changes to a branch if all I'm trying to do is pull down the latest changes.

[lszomoru]

We have recently added "Incoming/Outgoing" information in the "Source Control" view. These two new nodes also have dedicated actions to fetch/pull (incoming), and push (outgoing).

You can tweak the default settings so that the "Incoming/Outgoing" nodes are always shown:

  "scm.showIncomingChanges": "always",
  "scm.showOutgoingChanges": "always",

You can also use the git.showActionButton to hide the "Sync Changes" action button.