You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have read the latest README and followed the instructions.
I have read the latest GitHub Actions official documentation and learned the basic spec and concepts.
Describe your question
I am seeing the code cells of my .ipynb files rendered without formatting. I'm not exactly sure where to place this issue, I have it in jupyter-book too but haven't gotten any movement yet. If this is the incorrect venue for this issue, please let me know and i will close.
Public page: https://hydrosat.github.io/fusion-hub-docs/examples/order-service-example.html
Public repository: repo is private
YAML config: repo is private
YAML workflow: repo is private
Relevant log output
No response
Additional context.
No response
The text was updated successfully, but these errors were encountered:
I don't think this issue has any relation to this repo. This repo is an GitHub action to deploy to branches. It's not related to jupyter notebooks. Also the title of the issue is non-descript.
This issue has been LOCKED because of it being resolved!
The issue has been fixed and is therefore considered resolved.
If you still encounter this or it has changed, open a new issue instead of responding to solved ones.
Checklist
Describe your question
I am seeing the code cells of my
.ipynb
files rendered without formatting. I'm not exactly sure where to place this issue, I have it in jupyter-book too but haven't gotten any movement yet. If this is the incorrect venue for this issue, please let me know and i will close.jupyter-book/jupyter-book#1896
Relevant links
Public page: https://hydrosat.github.io/fusion-hub-docs/examples/order-service-example.html Public repository: repo is private YAML config: repo is private YAML workflow: repo is private
Relevant log output
No response
Additional context.
No response
The text was updated successfully, but these errors were encountered: