VS Code Atlassian Extension: Unable to create PR in Bitbucket
Clicking on ‘Create Pull Request' button in extension opens create new PR tab with broken UI and a dialog saying 'Failed to execute git’
Comments (6)
-
Account Deactivated -
reporter @{557058:a30b5736-f3cf-41d7-aad0-99c9ffac78ce}
Running
Git: Show Git Output
while adding PR gives following outputthere is one:
fatal: no upstream configured for branch 'feat/add-wrapper-classes'
for a local only repo which is understandable but then there are
Missing or invalid credentials
for the other 3 repos even though I’m logged in with the Atlassian extension as you can see in the bottom status bar. -
Account Deactivated @Ashutosh Shukla The extension uses
git
built in to VS Code for certain git operations. Looks like that is failing.- If you run
Git: Fetch
from command palette, does it show the same errors? - Does
git fetch
work when you run it on a terminal? Do you have to enter a password manually in that case? You may have to set up a credential helper if that's the case https://code.visualstudio.com/Docs/editor/versioncontrol#_remotes
If it works on terminal but not in VS Code, that could be an issue with VS Code and git setup. You can try cloning from an ssh url and see if that works better.
I've also found an old VS Code issue that sounds similar to this issue - https://github.com/microsoft/vscode/issues/1138. Some of the suggestions there might be worth trying out.
- If you run
-
reporter @{557058:a30b5736-f3cf-41d7-aad0-99c9ffac78ce} Thanks for the options.
I do enter password manually and
Git: Fetch
is also thowing the same error.Let me try using a ssh key for git
-
Account Deactivated @Ashutosh Shukla Were you able to try the ssh key route?
-
- changed status to closed
This issue has gone dormant, so I'm closing it. However, do reopen it or open a new issue if issues persist.
- Log in to comment
@Ashutosh Shukla Could you try a couple of things to help debug the error:
Git: Show Git Output
in VS Code's command palette to open the git output and let us know if you see any errors thereDeveloper: Toggle Developer Tools
from command palette) and check for any errors in the console theredebug
foratlascode.outputLevel
configuration in VS Code's settings UI (Preferences: Open Settings (UI)
) and check for logs in VS Code's output pane