You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hello all!
I'm a little confused when it comes to working with private repository in a team environment.
Scenario:
A private repo is created in my company's bitbucket account. As a team member, I'm supposed to clone it to my local and work from there. But when I try to do git clone (using https), I was asked to enter the password of the company's bitbucket account.
It seems strange that the company's bitbucket account password should be made known to all team members in order for them to clone.
Or is the recommended way to clone via SSH? If so, does it mean that all team members have to generate a SSH key and pass it into the repo in order to gain access?
Appreciate any input!
Thanks for the information! I'm beginning to understand how the access part works now!