nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Push from sourcetree to bitbucket always as team

Toon Van de Putte

We have a team on bitbucket called 'Klasse', currently with two members: myself and a colleague. I am the admin.

When I push from Source tree to the origin on bitbucket, this always seems to originate from the 'Klasse' team (the repository is owned by the team). When my colleague does a push, this is reflected correctly as coming from his individual account, and not from the team account.

I've spent all day looking at settings, resetting my ssh keys, restarting sourcetree, etc., to no avail.

Any ideas?

Accepted answers

All comments

KieranA

Hey Toon,

Sounds like your repository URL is the team URL rather than an individual URL. Check that out to make sure it reflects your user.

Cheers

Toon Van de Putte

I was under the impression that a repository only has one url: git@bitbucket.org:accountname/reponame.git (as mentioned here)

When I change 'accountname' to my username, the push fails because the repository isn't found.

When I log in to bitbucket, I don't see the repository in my profile either. I *am* listed as a user with read, write and admin rights in the repository's access mgmt screen. The team 'klasse' is listed as the owner and my colleague is listed as the creator.

KieranA

Hey Toon,

The account is the owner, which is the team, so the correct URL format would be the team name. Remember on Bitbucket that multiple people could have the same repo name within teams and of themselves, so there needs to be a per-user identifier. The 'ownership' of the repo is the team in this case.

Cheers

Toon Van de Putte

Yes, I realise there can be only one owner and a team repo only has one url. But how can I get my pushes to be associated with my account instead of the team account?

KieranA

Hey Toon,

I see what you want now. We don't support this in the user interface, but you can do this:

git config remote.origin.pushurl git@git.example.com:some/repo.git

So when you push it'll use a different URL to the one you're pulling from.

Hope that helps

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

sourcetree