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; } } }

multiple users accessing same repositories in source tree

Claire Bresee1

How can we have more than one user access the same repository in sourcetree? I saw this question answered already but the instructions are outdated. I've managed to create multi user access to these file commits in Bitbucket so far, but we all need to be able to commit and push from sourcetree.

Accepted answers

All comments

Tim Crall1

I'm a bit confused. Would these multiple people be working on their own individual workstations with a copy of SourceTree installed? If so, there should be no problem. Git is a distributed version control system. Your centralized repo is on Bitbucket, then each developer clones a copy of the repo to their own workstation, uses SourceTree or the git command line to add commits, and then pushes back to the centralized repo.

mkarda

I am actually interested in this as well.

In our case i have a local repository on one of our servers. I created the repository and access it through source tree. Someone else needs to access it as well through source tree. I put their login in the Bitbucket team so they can access it there, but when i added the working copy to his source tree it prompted for my login. Any thoughts? Or should i be looking for this in a Git forum instead of an Atlassian one?

Tim Crall1

Git is a distributed version control system. Each user should be working on their own clone of the repository.

mkarda

That makes sense, but say i have a folder in the website that is not really managed with the other code. It contains files that are not in the solution, so wouldnt get deployed when i build the site. I used a repo where the local is mapped right to the server drive. Im not the only one who needs to be able to manage this repository. And this folder does need to be in source control. I have to avoid the he-said she-said problem when images or js files change.

Tim Crall1

I'm not totally clear on your use case, but it sounds like maybe that directory should be it's own repo?

mkarda

The directory is its own repo, and 2 people need to be able to access it. We have the "remote" repo in bitbucket, no issue there, but the "local" repo is on our web server. Thats where multiple people would change it, or at least do a pull.

thinsoldier

In Bitbucket project settings under Access Management make sure their username is there and that you have them set to either write or admin.