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
our Enterprise Bitbucket server has changed URL: address and port are different
the old URL was kept as an alias
if we clone a Repository using the alias, then the VS Code extension does not work for Pull Request management
if we clone a Repository using the real address, or if we modify the remote information in a Repository cloned with the alias, then the VS Code extension works for Pull Request management
Conclusion: The VS Code extension does not handle URL redirection requests to access the Enterprise Bitbucket server.
Expected behavior
Support redirection url.
Screenshots
Environment and Version (please complete the following information):
Describe the bug
Since version 3.0.0, the extension does not support redirects (http status 301?) when accessing the Bitbucket server url.
See issue 802: Jira and Bitbucket extension for VS Code - No more local Git repository detection --> no redirection when remote is an alias of true URL
To Reproduce
The origin of the problem has been identified:
Conclusion: The VS Code extension does not handle URL redirection requests to access the Enterprise Bitbucket server.
Expected behavior
Support redirection url.
Screenshots
Environment and Version (please complete the following information):
Additional context
See Jira and Bitbucket extension for VS Code - No more local Git repository detection --> no redirection when remote is an alias of true URL
The text was updated successfully, but these errors were encountered: