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.
Hey Chan,
Welcome to the Bitbucket Cloud Community!
I would suggest performing the following command to view your list of configured remote connections and comparing these with the workspaceID that you are logged in to within the UI:
git remote -vvv
It is likely that you have entered a different email address that is not associated with the workspaceID for the repository that you are pushing to, and therefore you have instead signed up to Bitbucket Cloud using this email address and therefore have created a new empty workspace.
I would suggest verifying the workspaceID that you are pushing to ie workspaceID/repositoryslug and logging in to this workspace instead with its associated email address.
Hope this helps.
Cheers!
- Ben (Bitbucket Cloud Support)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.