-
Notifications
You must be signed in to change notification settings - Fork 11.4k
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
Error: Unknown tag 'toc' #1438
Comments
I have the same issue |
Does it work when you try it locally? |
I have also the same issue |
Solution: Setting of you the repository -> pages -> deploy from: select gh-pages branch , not the master brach. This solution taken from someone from closed threads and it worked for me :) |
Actually, the |
@DriesSmit is it working now? |
I faced the same issue and resolved using |
I am adding a comment here because, despite being linked in the README, this is not a complete solution. I am facing the same issue. The deploy process is failing during the build phase. the |
@ClonedOne trying to use as-is from the repo, changing only the name of the url in |
I have the same problem. It fails in the build and hence does not create the |
@Chiil have you tried a fresh start? Because if it fails from the very beginning it is an issue in the template itself, but if it was working before then it stopped, then the bug was introduced later, and it would be easier to debug. I always recommend from the beginning trying to deploy it as is, then adding some changes. |
Yes, I did, I forked the repository, pushed only one commit that changes the url and that is it. My repo is at https://github.com/Chiil/chiil.github.io |
Ok I just tried a fresh install with another user, and everything worked just fine. Here is the step-by-step I did (will update the README file soon): 1 - Start by clicking in
Created a public repo with name 2 - Go to
and give 3 - In 4 - Finally, go to
make sure that 5 - Wait until the GitHub actions finish, then simply navigate to |
Just realized that your username has capital letters. I hope that I'm wrong in this, but maybe this might be affecting it. |
It works now! I have noticed that the essential difference is whether to do "Use this template" vs doing "Fork". What is different that if I fork, the Github Actions is already set (correctly though), whereas when I use "Use this template" I can set it to read and write and things go OK. I am not sure whether I understand the difference. The capital letter made no difference. |
Sorry, have been out for a while and didn't check this. I ended up solving the issue by changing the "Build and deployment" setting to "Github Actions" and then accepting the default Jekyll configuration proposed by Github by clicking on the button below. |
Hello, I deployed the code with gh-pages but am facing the same issue still. |
Same. |
We need more information @danbischof. Is it a fresh install? Created from template or a fork? |
Fresh install and I face the same issue. Actually the error in build is thrown as soon as point 2. "In this new repository, go to Settings -> Actions -> General -> Workflow permissions and give Read and write permissions to GitHub Actions." Failing in the initial commit. |
Note: |
This is not needed since it will copy a lot of branches that you'll probably never use, and only pollute your repository with unnecessary code. |
This works for me. Thanks very much. @max870701 |
This works for me. Thanks @marsggbo |
Acknowledge the following
[For usage questions, please post in the Discussions instead of raising an issue.]
Describe the bug
I forked the repo as instructed. But the build then fails with the following message:
I tried the other solutions where I first set the branch in Pages to None. However it still fails to build. What is the recommended thnk to do here? Thank you for your time.
To Reproduce
I forked the repo and I am using an Ubuntu machine.
The text was updated successfully, but these errors were encountered: