quarto-dev / quarto-dev/quarto-cli
Improve how Quarto handles `.gitignore` to keep it clean
@cderv is already working on this.
Since Sep 7, 2026.
- Dominant language
- JavaScript
- Stars
- 6k
- Forks
- 458
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 41
Description
Discussed in https://github.com/quarto-dev/quarto-cli/discussions/6005
Originally posted by jakobarendt June 22, 2023
Description
Thank you so much to all for developing the incredibly powerful Quarto! I am currently writing my master's thesis with your software, and I am only starting to grasp what it can do.
One thing I have noticed, is that it makes some changes to my .gitignore file, when I run quarto render for my quarto book project. You have already explained this further in this answer.
In my case, however, it adds /.quarto/ as an item to the .gitignore file, even though I already have .quarto in it. To my understanding of the syntax, the latter is even more "restrictive" than the former in the sense that it always excludes .quarto directories/files independently of where are they are stored relative to the .gitignore file.
I imagine that you still had you reasons for implementing it the way it is now. Why does quarto render not acknowledge .quarto as a .gitignore parameter?
Another aspect that I want to mention here is that having quarto render acknowledge the more restrictive .quarto exclusion would make it more consistent with the R command usethis::git_vaccinate(), since there the ignore parameter is also .quarto.
Quarto version: 1.3.361
Machine: macOS Ventura 13.4
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.
Assessment
This issue has not been assessed yet.