Closed mcanouil closed 2 years ago
It appears, there was a CI workflow:
We have it this way by design. This repository is agressively simple because it's meant to also be a tutorial on how quarto extensions work, and we don't want the workflow yaml cruft to get in the way.
So if/when #10 is merged, how should the examples in gh-pages
be updated?
edit: I think I've got the answer (I "forgot" that the "new" publish option can be ran locally) 😅 => https://github.com/quarto-dev/quarto-actions/issues/22#issuecomment-1193401866 (ran by maintainers).
We'll do it ourselves :)
I noticed the rendered examples are published on
gh-pages
but there isn't any CI allowing the files to be properly updated on code changes inmain
. Should we (I) add something like: