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
Ruby Script automatically commits the exported files to GitHub or not.
Use time tag as commit-msg or not
Perhaps three Compile Formats: Dry-run, Export + Debug, and Export + Commit.
Outputs built to /export-mmd/docs locally and then committed to GitHub or committed and built by GitHub Actions.
Provide a showcase of the Quarto website and Quarto book.
The former option is not viable if we use a pre-release version.
The script will overwrite existing files but won't delete previously generated files that are no longer part of the project. Should we do something about this (or leave them to be manually erased)?
Cleaning the working folder before each export seems rather drastic and something to be avoided.
The text was updated successfully, but these errors were encountered:
This would be doable as some sort of paying work, but anything less would be untenable due to severe time constraints. Hopefully, I will be able to get around to it in the near future.
Questions:
Dry-run
,Export + Debug
, andExport + Commit
./export-mmd/docs
locally and then committed to GitHub or committed and built by GitHub Actions.The text was updated successfully, but these errors were encountered: