cloning the repo always returns an empty directory

[fastlane]

cloning the repo always returns an empty directory

[jessicathrasher]

My workaround was to follow the instructions for updating to a new version of boarding which will pull the code:

heroku git:clone --app [heroku_app_name]
cd [heroku_app_name]
git pull https://github.com/fastlane/boarding
git push

Now that you can see the code there you can make changes and push it back up to Heroku.

[Geeroz]

@boxenjim Have you ever get it to work? I'm having the same problem.

[joshdholtz]

This is a known issue for Heroic (https://help.heroku.com/XOBUHLKQ/why-do-i-see-a-message-you-appear-to-have-cloned-an-empty-repository-when-using-heroku-git-clone) and it appears that @jessicathrasher's solution is the correct on.

I don't understand why this would be happening from Heroku's end but 🤔 I will add this heroic link to the README

[vpolouchkine]

Can you post what you've done so far?

[schultzjim]

@vpolouchkine sure no problem.

1. followed these steps exactly: https://github.com/fastlane/boarding#getting-started everything worked as expected, app deployed and running, i only set the required env vars.
2. followed these steps exactly: https://github.com/fastlane/boarding#customize, on the cloning step it is always an empty directory

[vpolouchkine]

Looks like this is by design: http://stackoverflow.com/a/31609976/4802413

[wkwyatt]

@vpolouchkine Has this issue been resolved at all? I have been getting the same thing.

[dccarmo]

Did anyone find a workaround to this?