quarto-dev / quarto-dev/quarto-cli
`quarto-render --fail-if-warnings` not working as expected
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- JavaScript
- Stars
- 6k
- Forks
- 458
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 41
Description
I want things like misspelled filenames to trigger an error, especially in a CI job (which is awesome BTW https://github.com/quarto-dev/quarto-cli/discussions/439).
However, I don't get the non-zero exit code I would expect:
$ quarto render --fail-if-warnings
[ 1/14] file1.md
[ 2/14] file2.md
...
WARNING: Unable to resolve link target: intentional-typo.md
...
[13/14] file13.md
[14/14] file14.md
Output created: docs/index.html
$ echo $?
0
$ quarto --version
0.9.171
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the reported command with quarto render --fail-if-warnings and the unresolved intentional-typo.md link, using Quarto 0.9.171 or a current checkout. Trace how the warning affects the render command's exit status; done means the command returns non-zero when this warning occurs, suitable for CI.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 62/100