Hi! I’m trying to use Ghost’s Eleventy (11ty) starter. In the repo’s README, there’s a Deploy to Netlify button. When I click it, I’m taken to Netlify to create a new site using the starter. Netlify creates the repo for me, gets to work building the site, and says the build was successful. When I go to the site, it appears to be working fine. But when I go to the repo that was created for it, the repo is completely empty.
Is there something else I have to do, or is there a step I’m missing? I’ve used other Jamstack starters that worked fine and had fully populated repos, but I’m still kind of new with this stuff. I tried using the Deploy to Netlify button twice, and got the same behavior the second time as well. I posted on the Ghost forum about it, and they suggested I try here.
Hi, Edward! I didn’t try cloning first. I thought that the Deploy to Netlify button creates a repo and can’t be used with an existing repo. Is that wrong?
Thank you, Perry! I appreciate you looking into it.
I think the starter is actually set up to load https://eleventy.ghost.io/ and has to be edited to load the actual site (which in this case would be https://stoic-noyce-790cae.netlify.app/). That explains why the site appears to load fine despite the repo being empty, but there’s still the mystery of why an empty repo is generated in the first place.
Seems like a bug on our side, that the repo is not populated. I believe it only affects GitHub so if you use both, using GitLab will create the appropriate repo.
All we intended to do was push the contents of the old repo into the new one after the successful build, so you could do that yourself (git clone the template repo, remove .git directory w/history, then git push to the new repo) to repair it (before we get the bug fixed.)
Hey folks! We got a fix live for this yesterday. Let me know if you still have trouble using the button on that repo (and other repos with GitHub workflows enabled, which turned out to be the blocker)
It creates a repository (not technically a fork), and initiates a deploy, but the repository is empty (And the deploy fails, but that may be for an unrelated reason). I do have a GitHub Actions workflow in there. Any suggestions on resolving the issue?
I’ve had this setup for awhile and its worked great. A few months ago it stopped writing files into the repos and I was busy at the time on another project so I just left it.
But now I am back on this project and this is an important part of the equation, so it has to work.
It is a pretty simple Gatsby site, but does some shell scripting to replace files (this all works just great) but now suddenly, whenever you build a new site with the deploy to netlify button, whether you create a new netlify account or use an existing one, it sucessfully builds the site but the login for the cms stack fails. The Repo is created but it is empty. So it’s building a static version.
Oh and the parent repo is public… I checked. (I assume it needs to be public?)
Nothing out of the ordinary in the build logs… everything appears and works as it should… - just an empty github repo.
I’ve changed the order when we push the repository to the remote, so instead of doing it at the very end it’s basically the first step in the pipeline we perform. This now should give you a good glimpse of when something is failing and why as we log the errors:
I’ve tried to setup your project and indeed, it fails, but it fails with a very good reason – It seems that the repository has some secrets inside and GitHub push protection rejects that as it does not allow to push the secrets:
