I have admin privileges for two Bitbucket workspaces which I did not create.
When I compare the workspace settings for A and B, I notice that Workspace A is missing several options, including "SSH keys" and "APPS AND FEATURES".
Why can't I add SSH keys to Workspace A? Could this be a permissions issue?
For additional context, I'm asking this question because I believe it may be related to another issue I'm having: I cannot connect Workspace A to my Docker Hub account. Workspace B connects just fine.
Thank you in advance for your help!
I have identified another difference between Workspace A and Workspace B: I cannot create pull requests to Workspace B from any other workspace.
Note that the repo in Workspace A was forked from Workspace B:
Why can't I create pull requests from my Personal Workspace or Workspace B into Workspace A?
Another clue! In Workspace A, the Pipelines and Deployments pages show the repository creator's user name instead of the workspace name in the repo path:
Is this a bug?
Workspace B shows the workspace name like I would expect.
I contacted Atlassian support and they clarified the issue for me:
Unfortunately it is not possible to convert a personal workspace to a shared workspace. Instead, I need to create a new shared workspace and transfer all of my existing repositories from the personal workspace.
Hi, Bitbucket community! Are you a DevOps practitioner (or know one in your network)? Do you have DevOps tips, tricks, or learnings you'd like to share with the community? If so, we'd love to hea...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events