Build errors during deployment to GitHub Pages

[eftekhar-hossain]

**I am failed to deploy the ai-folio theme in my personal repository. Even I don't find any fruitful reason why it is happening.

Need Help**

[brucewlee]

same here

[alshedivat]

The website will not be correctly deployed until you make some changes, commit, and push. Please make sure to follow the deployment instructions provided in the README. See my comment below on how to deploy correctly.

[syncdoth]

Same here. What I did for my personal repo was:

1. fork the repo
2. rename the repo to <my user name>.github.io
3. change the name of the branch master to source
4. enable github actions
5. clone the repo to local
6. make some changes & push to source branch

Then, I get the same error as @eftekhar-hossain:

GitHub Pages failed to build your site.

The tag twitter on line 7 in _posts/2020-09-28-twitter.md is not a recognized Liquid tag.

Any ideas?

[raghavmittal101]

Got rid of this error by deleting the post mentioned in the error message. It's probably because of some mistyping.

[syncdoth]

@raghavmittal101 That did not help in my case.. :(

I deleted the _posts/2020-09-28-twitter.md file and re-committed and pushed, but similar error occurs on different file.

I presume the bibliography is the tag used for automatically fetching bibliography, so deleting this file also would not be a good idea..

[FloorVerhoeven]

Same here as @syncdoth

[alshedivat]

Looks like github made some updates recently, so there are a couple more steps you need to follow to setup a personal page:

1. As usual, fork the repository.

2. Click on Actions and enable Github Actions:

3. Go to Settings and rename your fork to <your-username>.github.io.

4. In the settings, select Branches and rename the master branch to source:

5. Finally, again in the settings, in the Github Pages section, set the source branch to master (NOT to source).

6. Make any changes to your webpage (in the source branch), commit, and push.

Point 5 is important and is the source of error. If GitHub Pages Source is set to source branch, it will attempt to automatically build and deploy your webpage. This results in the error because GitHub Pages does not support some of the jekyll plugins (bibliography, twitter, etc.). Instead, we use a custom github action for deploying the website (that's why you have to enable github actions on your fork in point 2), which correctly builds the website and pushes the built version to master. GitHub Pages simply picks up the built version of the website from the master branch.

[AndrewILWilliams]

@alshedivat thanks for this! Perhaps I'm being silly, but if we're renamed the master branch to source, I don't think we can then set the source branch to master in the Github Pages settings?

EDIT: Ignore this! You have to wait until Github Actions has run and generated a new master branch..

[lzfelix]

Is it okay if I make a PR adding these new instructions to the README.md?

[alshedivat]

@lzfelix, I wasn't sure how to update README without over-cluttering it. It'd be great if you could find a nice way!

[RajGhugare19]

@AndrewWilliams3142 How long does that take?

[alshedivat]

#261 adds the latest instructions to README. Closing this issue.

UPDATE: deployment of personal and organization pages has been simplified, see issue #342 and PR #344.

[danbischof]

This solution does not work for me. Followed all steps but cannot do 5. "Master" never appears here -- also not after waiting.

Thus, I still receive this error:

[arielsho]

Sorry, the updated instruction doesn't work for me. The "master" branch didn't show up automatically. Could you please help? Thanks! @alshedivat

Looks like github made some updates recently, so there are a couple more steps you need to follow to setup a personal page:

1. As usual, fork the repository.
2. Click on Actions and enable Github Actions:

1. Go to Settings and rename your fork to <your-username>.github.io.
2. In the settings, select Branches and rename the master branch to source:

1. Finally, again in the settings, in the Github Pages section, set the source branch to master (NOT to source).
2. Make any changes to your webpage (in the source branch), commit, and push.

Point 5 is important and is the source of error. If GitHub Pages Source is set to source branch, it will attempt to automatically build and deploy your webpage. This results in the error because GitHub Pages does not support some of the jekyll plugins (bibliography, twitter, etc.). Instead, we use a custom github action for deploying the website (that's why you have to enable github actions on your fork in point 2), which correctly builds the website and pushes the built version to master. GitHub Pages simply picks up the built version of the website from the master branch.

[vss245]

hey @arielsho, I had the same issue and I edited the 'deploy' file to say 'main' instead of 'master' because my first branch in the repo was named main (without renaming any other branches etc) - it seems to work so far.

Sorry, the updated instruction doesn't work for me. The "master" branch didn't show up automatically. Could you please help? Thanks! @alshedivat

[charleslipku]

@alshedivat thanks for this! Perhaps I'm being silly, but if we're renamed the master branch to source, I don't think we can then set the source branch to master in the Github Pages settings?

EDIT: Ignore this! You have to wait until Github Actions has run and generated a new master branch..

@alshedivat thanks for this! Perhaps I'm being silly, but if we're renamed the master branch to source, I don't think we can then set the source branch to master in the Github Pages settings?

EDIT: Ignore this! You have to wait until Github Actions has run and generated a new master branch..

I cannot see the new 'master' branch, do you know what is the reason?

[ghost]

@alshedivat yeah I dont have a new master branch

[LiquidAmmonia]

Until now, the bug still remains...

[chwag]

Until now, the bug still remains...

Had the same problem, and found issue #342, where it was proposed to set the default branch back to master (delete any other master branch you may have created in between) and set gh-pages as source branch for Pages. Worked for me! :)

[bicmfcs]

I keep getting build and deployment error while trying to publish my gh pages, it workes locally, does anyone could help me ?
Repository that I'm using.
I'm using jekyll al-folio for my webpage.
let me know if you need any more information.

[fastzhong]

Such bad UX on Github, forget about the Github pages/actions/workflows, use Netlify or Vercel.

[haiyun-he]

Until now, the bug still remains...

Had the same problem, and found issue #342, where it was proposed to set the default branch back to master (delete any other master branch you may have created in between) and set gh-pages as source branch for Pages. Worked for me! :)

work for me too!

[DiegoIBH]

I keep getting build and deployment error while trying to publish my gh pages, it workes locally, does anyone could help me ? Repository that I'm using. I'm using jekyll al-folio for my webpage. let me know if you need any more information.

I just re-run all jobs on the actions window and it worked.

[kun126]

Hi I just followed all the steps to initialise the webpage. The pages build and deployment works, while I keep getting an error from the Lighthouse Badger step in GitHub Actions:

lighthouse-badger-easy
Input required and not supplied: token

It seems to have no influence on the webpage itself. Would you suggest to ignore it or do something? Thanks

[gael-vanderlee]

Hi I just followed all the steps to initialise the webpage. The pages build and deployment works, while I keep getting an error from the Lighthouse Badger step in GitHub Actions:

lighthouse-badger-easy
Input required and not supplied: token

It seems to have no influence on the webpage itself. Would you suggest to ignore it or do something? Thanks

Same here

[george-gca]

This issue was closed years ago and is related to another error, so this should be treated in another issue.

About our workflows, check our FAQ.