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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


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
Community Members
Community Events
Community Groups

How do you import a private git repository?

I have a private git repository on my PC and want to import this repo into bitbucket.  Is there an easy way to do this?


1 answer

1 accepted

2 votes
Answer accepted
Mikael Sandberg Community Leader Oct 02, 2020

Hi @ekennedy80,

Welcome to Atlassian Community!

To import a local repository this is what you need to do:

  1. Create a new repository in Bitbucket if you have not done so yet.
  2. Get the new URL for the repository by clicking Clone and copy the URL
  3. In your local repository, set the new remote URL by running this command:
    git remote add origin <repository URL>
  4. Push everything back to Bitbucket by running this command:
    git push -u origin master

When I try to push I get the following - I assume its because the bitbucket repo is not as empty as we'd like? - it has a and .gitignore which I dont want/need? how do I force the push to overwrite the nearly empty bitbucket?

! [rejected] master -> master (non-fast-forward)
error: failed to push some refs to ''
hint: Updates were rejected because the tip of your current branch is behind
hint: its remote counterpart. Integrate the remote changes (e.g.
hint: 'git pull ...') before pushing again.
hint: See the 'Note about fast-forwards' in 'git push --help' for details.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events