I started migrating to Bitbucket some time ago. The number of my personal repositories are growing steadily, and I am starting to struggle keeping an overview.
I'd love to organize my repositories. Basically, what I need are groups/folders (ideally nested, but one layer would be ok for now). Projects seem to be a nice fit, but they only exist for teams. These repositories, however, are just for me.
So, what is the best practice for this use case?
(Or am I, once again, the only user on Bitbucket with such a Problem?)
Do I need to create a "me" Team only consisting of my personal account, so that I can host my personal projects only I will work on? Sounds wrong to me. Especially, since there would be URL-Differences between "Me" and my "Me" Team. This is already confusion ... me.
I only want to group the repositories for the better overview. This does not have to be reflected in the URLs oder IDs or whatever.
No you are not the only one with such a problem.
I think in the long run it would be better to create a team because you'll be able to group your repositories and filter them in the dashboard.
One team is all you needs since it is able to create an unlimited number of projects so that would give you your one layer. (Yes I use a team)
But of course this will change the URLs so there would be a one time setup cost.
If you want to keep it simple you could just use your main account to own the repositories and organize it with folders in SourceTree.
Just a comment for people finding my questions:
I don't care for URLs, but Repository names. These Names=IDs only live withing the Team's Namespace, not the projects' Namespace. Thus no two projects can both contain repositories called by the same name, e.g. "Documentation".
I would need to
This feels even more weird than using one team. But this seems to be the best option atm.
I going to change the repositories' URLs anyway...
Thanks, this is good to know before I jump into importing a bunch of repositories.
The first option is probably what I will go with since I am working with a few people. We will end up with folders that just have these redundant names.
I think the repositories don't live in the project name space, because you may want to share repositories between projects. So you could have something like: Project1 >SharedLibrary >Project1Files >Project1Docs Project2 >SharedLibrary >Project2Files >Project2Docs Not that that would be good practice. I'm no expert.
You cannot share repositories between projects.
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot