Skip to content

Commit e1e3d25

Browse files
authored
Update example-06-no-render.md
1 parent 4636bcf commit e1e3d25

File tree

1 file changed

+6
-8
lines changed

1 file changed

+6
-8
lines changed

examples/example-06-no-render.md

Lines changed: 6 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
# Using Quarto Actions: do not render
1+
## Publishing without rendering
22

33
By default, `quarto publish` will re-render your project before publishing it.
44
However, if you store the rendered project in version control, you don't need
@@ -13,13 +13,12 @@ to the `publish` action:
1313
render: false
1414
```
1515
16-
## Chaining render then publish
16+
## Rendering a single format
1717
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:
2019

21-
* `quarto render` by providing the targer output format
22-
* `quarto publish --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)
2322

2423
```yaml
2524
- 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
3231
with:
3332
target: gh-pages
3433
render: false
35-
path: ${{ env.QUARTO_OUTPUT }} # define this env var if you are using a non default output-dir
36-
```
34+
```

0 commit comments

Comments
 (0)