Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Expose git.publish as a command through Git API

See original GitHub issue

The git.publish command would be very helpful to have in the API itself. Right now, push is very limited in that everything needs to already be set up for the user before we can push, but publish has a really great UI experience to help the user with everything.

Issue Analytics

State:
Created 3 years ago
Comments:7 (7 by maintainers)

Top GitHub Comments

1reaction

nturinskicommented, Nov 6, 2020

Yes, but I haven’t been able to catch any errors (if the repo you try to publish has no commits, for instance).

On a side-note, it would be nice if the publishRepository didn’t await the information window to view the repo in GitHub since it’s easy for a user to miss, but if used as part of a step, won’t proceed to the next step until a user clicks something (either view or X)

0reactions

joaomorenocommented, Nov 11, 2020

Another unrelated note, but publish also defaults to the authenticated user so a user can’t create a repo in an authorized organization through VS Code.

https://github.com/microsoft/vscode/issues/98349