-
Notifications
You must be signed in to change notification settings - Fork 509
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
empty repository #19
Comments
Same |
I have the exact same problem |
Try using: This allows you to pull the github repo into your directory. See more here: https://kb.heroku.com/why-do-i-see-a-message-you-appear-to-have-cloned-an-empty-repository-when-using-heroku-git-clone |
Similar to #13. Although the resolution in that thread leads to a dead link. Try this: https://help.heroku.com/XOBUHLKQ/why-do-i-see-a-message-you-appear-to-have-cloned-an-empty-repository-when-using-heroku-git-clone |
Can no longer reproduce, this should probably be closed! :) |
when trying to clone to local machine after setting up bot, the following appears:
warning: You appear to have cloned an empty repository.
The text was updated successfully, but these errors were encountered: