can not see repositories in Atlassian bitbucket vscode extension
Asked by Mohamed Fahmy:

i have Atlassian extension setup with a custom site for both Jira and Bitbucket.

the Tickets for Jira do show up in Vscode but for some reason Bitbucket never manages to connect to any repository. i always have "no bitbucket repositories found in this workspace"


Answers:
author: Joseph Leiba
body: The Atlassian extension for VS Code is riddled with inconsistencies between itself and the Bitbucket APIs.

To use personal access tokens with your Bitbucket site, Atlassian says in [this article](https://support.atlassian.com/bitbucket-cloud/docs/using-access-tokens/) to specify remote URLs using a format like below:

```
https://x-token-auth:{repository_access_token}@bitbucket.org/{workspace}/{repository}.git
```

But of course, the Atlassian extension doesn't work at all with URLs of that form. You get "  
URL parsing failed" errors in the extension logs. The Atlassian extension is nothing if not inconsistent.

[Using Repository Access Tokens \| Bitbucket Cloud \| Atlassian Support](https://support.atlassian.com/bitbucket-cloud/docs/using-access-tokens/)

comments: author: Joseph Leiba
body: The above problem is another reason you may see the message, "No Bitbucket repositories found in this workspace".

What's worse, today suddenly the Atlassian extension stopped offering the option to specify a Personal Access Token in the authentication configuration of your custom Bitbucket site. Now it allows only username/password, which is why I am trying to specify the token in the URL. This extension is constantly breaking in new ways and never being fixed.


author: Tobias
body: Keeping this extension doing its work is frustrating, thats why I stopped using it.


author: Vytenis Ku?iauskas
body: VSCode changed and deprecated git functionality for getting repositories

<https://github.com/microsoft/vscode/blob/27f15db3c1ec3155c8c65797fe0c8d978e59d0bf/extensions/git/src/api/api1.ts#L38>

So the issue should be fixed on Atlassian side

comments: author: Nic Brough -Adaptavist-
body: Actually, no, VSCode is the client, not the service. It's up to clients to support the services they are clients for, it's not up to a service to provide things that they don't want to.

VSCode and/or Github need to fix this, not Atlassian. In this case, there's nothing Atlassian could do, they don't either of the services that have the problem. Bitbucket is stuck in the middle.


author: Ernest Zapata
body: I went back and installed extension version 2.10.2 which does find my local repositories


author: FDisk
body: [@Nic Brough -Adaptavist-](/t5/user/viewprofilepage/user-id/781454) no actually you are wrong. The extension is using vscode internal functions and they changed. Why it was changed is a different story.


author: Nic Brough -Adaptavist-
body: Eh? I said the service has not changed, but the client has, exactly as you say too.


author: yakirgb
body: I see same issue with latest Atlascode plugin: 3.0.3, any workaround ?


author: FDisk
body: did your vscode is up to date? In my case

vscode version: 1.77.0  
and plugin 3.0.3

this combination works for me


author: yakirgb
body: I'm using latest vscode 1.77.0 too,  
with Bitbucket version v7.4.0


author: yakirgb
body: Any ideas how to debug the issue of "no bitbucket repositories found in this workspace" ?


author: tidhar_klein_orbach
body: I noticed that my remotes were configured:  
*ssh://git@bitbucket.mycompany.com:7999/myrepo.git*

<br />

so I added another remote with the same url without the "ssh://" *git@bitbucket.mycompany.com:7999/myrepo.git*

<br />

after that I was managed to see the repository in vscode.


author: yakirgb
body: Replace "ssh://" with "https://" resolved the issue.

I think there is a bug with "ssh://"


Tags: bitbucket-server

server