You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I found one other issue with the Bitbucket client. When a repository is created in Bitbucket the HTTP clone URL can have different formats depending on what the admin settings are for the repository or server.
The default clone URL from Bitbucket only includes the username but it looks like the current client setup is hard coded to use a URL with the username and password. Here's an example of the difference:
The zoekt client will currently fail to clone the repository unless it uses the custom format with a username and password.
I had a hard time finding this called out explicitly in the Bitbucket docs but this page shows an example of the default clone setup.
Could the default clone URL be the username format? Then maybe a Bitbucket option could be added to the config to allow the custom username + password URL to be used?
The text was updated successfully, but these errors were encountered:
Hi, I found one other issue with the Bitbucket client. When a repository is created in Bitbucket the HTTP clone URL can have different formats depending on what the admin settings are for the repository or server.
The default clone URL from Bitbucket only includes the username but it looks like the current client setup is hard coded to use a URL with the username and password. Here's an example of the difference:
https://{username}@bitbucket.org/{repo}.git
https://{username}:{password}@bitbucket.org/{repo}.git
The zoekt client will currently fail to clone the repository unless it uses the custom format with a username and password.
I had a hard time finding this called out explicitly in the Bitbucket docs but this page shows an example of the default clone setup.
Could the default clone URL be the username format? Then maybe a Bitbucket option could be added to the config to allow the custom username + password URL to be used?
The text was updated successfully, but these errors were encountered: