Push command and button push to wrong branch? about vscode-gitlens

[jkelroy]

Hello @borisghidaglia, can you expand on exactly what is not working as expected? Is the issue that it shows push to origin/dev (when that is not the actual upstream), that pushing will push to another branch besides origin/dev or that origin/dev is being set as the upstream unexpectedly?

Notably, if you create a branch in GitLens, the upstream will be automatically set to the upstream of the branch you created off of - we have a feature request to prompt for this here. So if the issue is that the upstream is being set to main expectedly for you, then the linked feature request should help solve for this.

[borisghidaglia]

Hello @jkelroy, thanks for your answer :)

Is the issue that it shows push to origin/dev (when that is not the actual upstream) [...]

Yes exactly. It pushed to origin/dev when I expected it to push to origin/feature/my-feature, as my current branch was feature/my-feature.

From the issue you're sharing:

[...] when creating a branch from a remote only branch [...]

Thanks I understand now, it is probably what I did. I tried and indeed the upstream is set to the upstream of the branch I created off of.

But why is this the default behavior?

[jkelroy]

Duplicate of #2778

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.