If you have computational content which cannot be executed in a CI environment (because of eg security or authentication), you can use Quarto's freezer feature.
Add the following to your _quarto.yml
configuration:
execute:
freeze: true # never re-execute computational content during project render
This stops quarto from re-executing computational cells during a project render.
From a computer that is capable of executing the content, run a file-specific render
command to create or update the frozen content
$ quarto render name-of-file-to-freeze.qmd
Note that you have to specify the particular file: a call to quarto render
will not re-execute the content when freeze: true
. Finally, add the _freeze
top-level directory to version control so that GitHub Actions can reuse the executed content.
See Quarto's documentation on freeze for more.