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
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
I believe there is a small issue with the "You have an empty repository" screen displayed by BitBucket Server 7.9.0 which could cause later problems for situations where the repositories are not intended to use the default "master" branch name any more. If an empty repo is created by the Project administrator with a default branch name of "main", I believe the instructions that show on the page for "My code is ready to be pushed" should be slightly different. Specifically, the line "git init" on those instructions should be "git init -b main". Otherwise, git will create the new repo with the default branch name matching that user's locally configured default branch name (which still defaults to "master"). The line "git push -u origin HEAD:main" will workaround this in the short term by setting up so that whatever their local branch name ends up being, it will be linked to the correct branch name on BitBucket. However, it still sets up a situation where they have a local branch that does not match names with its associated BitBucket branch.