GitHub Pages Builds Fail #22007
-
I’m trying to create a website using Github Pages. The website has been building fine in the past. Today I updated some of the html and the website wouldn’t build anymore. I tried reverting to the previous commit, but it wouldn’t build either. I read the troubleshooting page, to no avail. I don’t have any idea of what to do anymore, please help. The error:
My repository: https://github.com/carterchannui/integratedesports.com |
Beta Was this translation helpful? Give feedback.
Replies: 12 comments
-
Hello @carterchannui, If you’re not using Jekyll to build your website, sometimes GitHub pages will mistake certain characters, specifically curly braces, as jekyll objects, tags, etc. causing your page build to fail. If you’re just using static HTML pages (which is what it looks like to me), the easiest and quickest fix would be to disable Jekyll processing, which can be done by creating a file named .nojekyll in the root of your pages repository. |
Beta Was this translation helpful? Give feedback.
-
Hi @sethclydesdale, If by static you mean without animations, I don’t believe my website is just static HTML. This is what the website looks like: https://integratedesports.com/#hero. Also, why has it just started failing? It wasn’t doing this before. |
Beta Was this translation helpful? Give feedback.
-
By static, I meant a website that’s created with HTML (no back-end coding). This has a pretty good explanation. Anyway, checking your repo, I’m seeing errors like the one below.
I’m assuming it may be mistaken for Jekyll liquid code. If you’re not using Jekyll, I would suggest creating a file named .nojekyll (it doesn’t need any contents) in the root of your repository to see if it resolves the errors. If you are using Jekyll, then handling the file in the error above should resolve the issue as well. |
Beta Was this translation helpful? Give feedback.
-
Thank you @sethclydesdale, creating the .nojekyll file effectively worked. The website has updated and was built successfully. GitHub did send me an email that I would like understand:
What does this mean? Is it telling me to switch to a different program? |
Beta Was this translation helpful? Give feedback.
-
Good to hear! No, it’s more of a suggestion to keep large binary files (.exe, for example) to the releases section, since they can go towards the recommended 1GB limit for repositories. If the files are necessary for your website to function then you can keep them as is. If not, then you can always remove them to keep your repo’s size down. |
Beta Was this translation helpful? Give feedback.
-
The documentation of this feature is a bit missleading. Is the If in the master branch, it seems to me that it should also be possiable to put it in the root of whereever the pages is served from. But that is just my opinion :slight_smile: |
Beta Was this translation helpful? Give feedback.
-
I had that problim too, and this solution solved it … thanks alot |
Beta Was this translation helpful? Give feedback.
-
I had the same problem and was glad that the suggestion creating a .nojekyll file solved the problem and my site was successfully published. |
Beta Was this translation helpful? Give feedback.
-
I am having a problem building |
Beta Was this translation helpful? Give feedback.
-
I’m having the same problem and I already have a |
Beta Was this translation helpful? Give feedback.
-
thank you… I had the same problem… But I fixed it by saw your solution. many many thanks |
Beta Was this translation helpful? Give feedback.
-
this actually solved my problem, Thanks |
Beta Was this translation helpful? Give feedback.
By static, I meant a website that’s created with HTML (no back-end coding). This has a pretty good explanation. Anyway, checking your repo, I’m seeing errors like the one below.
I’m assuming it may be mistaken for Jekyll liquid code. If you’re not using Jekyll, I would suggest creating a file named .nojekyll (it doesn’t need any contents) in the root of your repository to see if it resolves the errors. If you are using Jekyll, then handling the file in the error above should resolve the issue as well.