Git - Support the "push.default=current" strategy

[AndreyBelym]

I experimented with the push.default strategies and discovered that the "Sync" button in the "Source Control" tab in the Activity bar and the "Git: Push" command in the Command Palette in VSCode 1.78.2 does something unexpected (for me at least) when git's push.default config is current and a local branch is tracking some remote branch with a different name.

I expected that VSCode will respect the setting and will behave similarly to the default push (git push without arguments), pushing changes to the remote branch named as a local branch instead of pushing the to the tracked upstream branch. Unfortunately, it didn't happen, VSCode still pushes new changes to the upstream branch.

Steps to reproduce:

1. Setup a branch that tracks some remote branch with a different name:

$ git checkout -b feature/do-some-stuff origin/main

2. Set push.default to current:

$ git config push.default current

3. Do some stuff

$ git push --allow-empty -m test

4. Push with the git CLI. The remote feature/do-some-stuff is created and updated.

$ git push
To <origin>:
 * [new branch]      feature/do-some-stuff -> feature/do-some-stuff

5. Push with the "Sync" button and/or use the "Git: Push" command. It pushes changes to the remote main branch. I would expect that it will push to feature/do-some-stuff, as in step 4 (especially for the command).

<Press Sync>
<Git Output tab:>
To <origin>:
   f649920..9d6b5fc  feature/do-some-stuff -> main

[bstaeheli]

I'm also affected by this issue. When creating feature/bug branches from main in VS Code, the branch..merge config is incorrectly set to refs/heads/main instead of the branch itself. This causes VS Code to attempt pushing to main instead of the same-named remote branch, even though I have push.default=current configured globally.

The command line respects push.default=current correctly, but VS Code's Git extension ignores this setting and always uses the upstream configuration.