Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Bug: cloning via HTTPS broken after Atlassian account transition

veksler September 20, 2016

Cloning with HTTPS is broken after the Atlassian account migration.

The clone path is "git clone https://veksler@bitbucket.org/feeorg/fee-cms.git"

"veksler" is my Bitbucket username.  This username does not work after migrating my Bitbucket account to my Atlassian account.  When I clone with SourceTree I get a credential error, and the username is read only, so I can't use my Atlassian credentials.

The workaround is to remove the username from the clone path in the Repository Settings.  This is annoying because I have more than 10 repositories in my SourceTree.  However SourceTree is still asking me for the old Bitbucket account - it must have the old credentials hidden somewhere.

login.png

1 answer

0 votes
Alastair Wilkes
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
September 20, 2016

Hi David

You should be able to authenticate using your Bitbucket username and your Atlassian account password. Does that work?

Alastair

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events