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
Copy file name to clipboardExpand all lines: examples/example-06-no-render.md
+6-8Lines changed: 6 additions & 8 deletions
Original file line number
Diff line number
Diff line change
@@ -1,4 +1,4 @@
1
-
#Using Quarto Actions: do not render
1
+
## Publishing without rendering
2
2
3
3
By default, `quarto publish` will re-render your project before publishing it.
4
4
However, if you store the rendered project in version control, you don't need
@@ -13,13 +13,12 @@ to the `publish` action:
13
13
render: false
14
14
```
15
15
16
-
## Chaining render then publish
16
+
## Rendering a single format
17
17
18
-
By default, `quarto publish` will render to all format defined before publishing.
19
-
If you need to customize the rendering step, e.g only render one format in CI before publishing, use a two step process:
18
+
The `render: false` choice is all-or-nothing. If you need to customize the rendering step, e.g. only render one format in CI before publishing, use a two step process:
20
19
21
-
* `quartorender` by providing the targer output format
22
-
* `quartopublish --no-render` to skip re-rendering before publishing
20
+
* use the `quarto-actions/render@v2` action and provide a target output format (in this example YAML configuration, we use the HTML format)
21
+
* use the `quarto-actions/publish@v2` action with `render: false` to skip rendering before publishing (in this example YAML configuration, we publish to GitHub Pages)
23
22
24
23
```yaml
25
24
- name: Render Book project
@@ -32,5 +31,4 @@ If you need to customize the rendering step, e.g only render one format in CI be
32
31
with:
33
32
target: gh-pages
34
33
render: false
35
-
path: ${{ env.QUARTO_OUTPUT }} # define this env var if you are using a non default output-dir
0 commit comments