Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Git: Push with tags should do everything Git: Push does. #70081

Closed
waynebloss opened this issue Mar 8, 2019 · 1 comment
Closed

Git: Push with tags should do everything Git: Push does. #70081

waynebloss opened this issue Mar 8, 2019 · 1 comment
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug git GIT issues help wanted Issues identified as good community contribution opportunities verified Verification succeeded
Milestone

Comments

@waynebloss
Copy link

waynebloss commented Mar 8, 2019

I tried to standardize on using the Git: Push with tags command because I always forget to push new tags. However, Git: Push with tags does not do everything that the normal Git: Push command does.

For instance, if the branch doesn't exist on the remote yet, Push with tags does not ask the user to publish.

Also, Push with tags fails silently instead of showing an error for a failure, e.g. "fatal: no upstream configured for branch 'vnext'".

@vscodebot
Copy link

vscodebot bot commented Mar 8, 2019

@vscodebot vscodebot bot added the git GIT issues label Mar 8, 2019
@joaomoreno joaomoreno self-assigned this Mar 11, 2019
@joaomoreno joaomoreno added bug Issue identified by VS Code Team member as probable bug help wanted Issues identified as good community contribution opportunities labels Mar 11, 2019
@joaomoreno joaomoreno added this to the June 2019 milestone Jun 12, 2019
@RMacfarlane RMacfarlane added the verified Verification succeeded label Jun 26, 2019
@vscodebot vscodebot bot locked and limited conversation to collaborators Jul 27, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug git GIT issues help wanted Issues identified as good community contribution opportunities verified Verification succeeded
Projects
None yet
Development

No branches or pull requests

3 participants