Closed paciorek closed 10 months ago
Thanks!
code-cell
directive did not work as documented for me. That is, I could not get myst to hand off the code-cell blocks to a jupyter kernel. I was able to itegrate .ipynb files without any trouble -- they are already executed.myst init --gh-pages
, or does that do something more than create the deploy.yml
file?I updated the text of the warning about non-run code in the code-cell
directive to give more information.
After some discussion, we realized that departmental staff will likely be the ones to fork the template or previous repo. This means that avoiding the initial action failure is not that big of a deal, although we do document it for ourselves.
Here's what I noticed:
schedule.md
. We need to change that to indicate the schedule is onindex.md
and perhaps say something about the use of cards.myst init --gh-pages
, MyST tries a deployment that fails based ondeploy.yml
, so the user will get an email indicating that failure (e.g., here's a failure from my test).myst init --gh-pages
it tells the user they need a new name for the deployment yml file, and then one would have two GH actions.myst init --gh-pages
.