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,455,410
Community Members
 
Community Events
175
Community Groups

can't clone a repo in git bash

Edited

I am trying to clone my repo from bitbucket to my pc but  when I pasted the URL using git bash it displays message cloning into ' repo name ' and it only creates an empty folder. Not able to resolve it. plz help

1 answer

0 votes
Syahrul Atlassian Team Jan 12, 2022

Hey @Anjana Kapoor 

G'day!

There are multiple reasons that the clone succeeded and the folder is empty let's explore some of them.

Check if there's any content in the folder by using bash to navigate into the folder and run "ls -lah" this will list out all the files even the one hidden. If there's a file then the issue would probably be because the files were hidden so try running "git branch -a" to list out the branch in your repositories and "git checkout the <branchname>" to start working on the branch

Another common issue is that you are using outdated git, so please download and install the latest git then navigate into the folder via terminal and check if git initiates accordingly.

If both didn't work then most likely the issue is with the cloning steps themselves and we may need to further investigate by running the following verbose commands when re-cloning the repositories:
If you use HTTPS:

GIT_TRACE_PACKET=1 GIT_TRACE=1 GIT_CURL_VERBOSE=1 <git clone command>

If you use SSH:

GIT_TRACE_PACKET=1 GIT_TRACE=1 GIT_SSH_COMMAND="ssh -vvv" <git clone command>

Let me know how it goes

Cheers,
Syahrul

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events