This is what we made Kyso for - the linked post is actually a Jupyter notebook itself, the code is hidden by default to make it readable to non-technical people but you can click on the "code hidden" button on the top right to see the code in full.

If github is not working for you well for your notebooks. You can try Kyso by signing up and importing your notebook from Github directly on this page: https://kyso.io/github, or upload it using this page: https://kyso.io/create/study

Disclaimer - I am OP and founder of Kyso

You made Kyso for making GitHub-hosted Jupyter Notebooks render when accessed with a web browser on github.com?

Well, it's one of the ways to post to Kyso, but yeah, you can synchronize your Github repositories to Kyso and choose the notebooks you want to have rendered. When you push changes to the repo, the sister post on Kyso will be automatically updated.

I get it a lot, so I set a precommit hook to render all my notebooks to HTML. With GitHub Pages, I can access them easily.

Sounds useful, care to share that hook?

I've gotten this as well after uploading notebooks to github. It usually goes away for me after ~10mins after I've uploaded the .ipynb. I'll check this out though, thanks!

thanks for linking there, tried to make some ruby notebooks and works quite well https://nbviewer.jupyter.org/github/localhostdotdev/notebook... (very similar to the github interface though)

I don't think it's just you, I've been getting them too. It's probably Github timing out trying to render the notebook.

Re: this - it would be fun to set up a Beowulf cluster of Jupyter notebooks, if you will, and just upload them to Github for free parallell computations.

(Obviously this would be for shits 'n giggles, not any serious work).

GitHub and nbviewer don't actually execute the notebooks, they simply render the markdown, code, and saved output to HTML.