Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,359,866
Community Members
 
Community Events
168
Community Groups

Submodule with different user fails to clone/push with Sourcetree

We have few submodules configured in the main bitbucket cloud repository of our project. We would like configure those submodules to get cloned automatically when the main repository is cloned.

The submodule Source path / URL  is configured as

https://userA@bitbucket.org/xxxxxxxxx/module.git

When userA tries to download this submodule, no issues found.

 

But when userB clones the main repository and submodule. The submodule cloning fails.

While cloning the submodule SourceTree prompts userB to authenticate the Atlassian account via userA.

 

Right now, to clone these submodules in userB's machine, we change the username(userA to userB) in the URL path every time,

https://userB@bitbucket.org/xxxxxxxxx/module.git

Question:

How to configure the submodules generically so that it can be cloned without changing the username in the URL path?

 

 

1 answer

1 accepted

0 votes
Answer accepted

The https clone is associated with userid. So the username has to be changed when using https.

 

Use the command as "git clone git@bitbucket.org:xxxxxxxxx/module.git" to clone in gitBash. The command will not have userid associated with it. So it can be used independent of users. gitBash need installed, set up ssh key, and authenticated with password. All of these are one time activity. Once done, user will have access to all modules and can clone any module.

So using gitBash will be the short answer to your issue.

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Sourcetree

Bug Fix: Sourcetree for Windows authentication error when updating to app password

Hello Sourcetree users!!! With the recent removal of Bitbucket Cloud account passwords for app passwords (please see our Bitbucket Cloud community post for details on why we made this change for se...

78,669 views 134 29
Read article

Atlassian Community Events