-
Notifications
You must be signed in to change notification settings - Fork 658
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: Couldn't find a Table of Contents file. #2078
Comments
Thanks for opening your first issue here! Engagement like this is essential for open source projects! 🤗 |
Updates: manual build works, but not with the GitHub Action workflow.
|
This was caused by a recent bug in our cookiecutter, fixed by executablebooks/cookiecutter-jupyter-book#43 Could you try modifying your jupyter-book build . with jupyter-book build <NAME-OF-YOUR-BOOK> where |
I updated the build command as well as the path as follows:
Now I am getting this error:
You can checkout my deploy.yml file here: https://github.com/hydroaggie/group_handbook/blob/main/.github/workflows/deploy.yml |
It looks like GitHub might be experiencing an outage. Let's try again once https://githubstatus.com is all green. |
Describe the bug
context
After creating Jupyter Book using this cookie-cutter template: https://github.com/executablebooks/cookiecutter-jupyter-book, I was able to push the book to Github (https://github.com/hydroaggie/group_handbook) and saw the live document on Github Pages.
Now I am trying to update the book content.
expectation
I expected the book to be built without error.
bug
Here's an error message I ran into when I committed the changes and pushed to github:
Reproduce the bug
The steps on how to create my Jupyter Book is published here: https://hydroaggie.github.io/blog/2022/Create-Jupyter-Book/
You can reproduce the error following the steps.
List your environment
Jupyter Book : 0.15.1
External ToC : 0.3.1
MyST-Parser : 0.18.1
MyST-NB : 0.17.2
Sphinx Book Theme : 1.0.1
Jupyter-Cache : 0.6.1
NbClient : 0.5.13
The text was updated successfully, but these errors were encountered: