Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

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,463,768
Community Members
 
Community Events
176
Community Groups

Bitbucket cloud allows ONLY read access using key pairs

Now that so many of us are migrating to bitbucket after the dark side acquisition of github, it will help a LOT if the bitbucket migration guide states clearly that:

The free "bitbucket cloud" account does NOT allow key pairs to be used to push changes.

My keypair access works fine (it's easy to set up, just like github). I can pull just fine.

What I discovered, after the fact (and after migrating 5 repos), is that the dashboard DOES NOT allow me to change the key access away from "read". The Atlassian documentation I've found for changing this applies ONLY to "Bitbucket server" accounts.

I don't mind paying for "bitbucket server", I already paid for github and price is NOT the reason I'm ditching github. Please do me, and us, the favor of being clear about what your offerings do and do not do.

Now I have to go create a "Bitbucket Server" account and apparently do these imports all over again.

Please ... don't be evil.

1 comment

I found the answer.

Each bitbucket user account also includes key access. I was looking at the "key access" setting on the dashboard of a specific repo.

When I added my key to my user settings, all was fine.

The UI and documentation might perhaps be more explicit about this.

Comment

Log in or Sign up to comment
TAGS

Atlassian Community Events