-
Notifications
You must be signed in to change notification settings - Fork 5
Add Myst (new tech stack) workflow #50
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
base: main
Are you sure you want to change the base?
Conversation
05fd475
to
f66517d
Compare
613fb20
to
eab84c9
Compare
48eb9a5
to
6226b82
Compare
Result of 💾 Updating .gitignore ✅ Project already initialized with config file: myst.yml ✅ Site already initialized with config file: myst.yml.
Note: jupyter is required for myst execution engine.
- Fail if tracebacks found in myst execution log. - Preserve log and err on traceback.
One (of the many) goals of this project I think should be to serve as a "transition guide" from the existing myst-nb/sphinx stack to the Massive improvement (IMO)
Needs
|
Can we merge this? I mean even without the CI preview I feel this is a great addition, so no need to wait for the PR to develop some code-rot. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Needs a rebase obviously, but content-wise, let's have this in!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK, well, I was overly enthusiastic, as the landing page still needs some TLC to look more like the page with the old stack.
E.g. I would even go as far as to say myst
forcing the first toc item to be a file:
is rather inconvenient here (and was also in my other repo)
Simplest possible setup (with minimal instructions) for getting up and running with
myst
.