quarto-dev / quarto-dev/quarto-cli

Copy empty directories with `quarto use template`

Open
#12,750 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement extensions
Dominant language
JavaScript
Stars
6k
Forks
458
Avg merge
1d 9h
Merged PRs (30d)
41

Description

I was excited to learn that part of project management can be automated with quarto use template. I try to keep file organization consistent for any new analysis project that I start, so it would be ideal to be able to copy empty directories from github repos.

The approach I tried was creating this github repo: https://github.com/robert-koetsier/r-analysis/tree/main, containing the _quarto.yml file that I want to copy for new projects, and several directories that only contain .gitkeep files to ensure that the directories are tracked by git. I prefer not keeping useless files for every project, so I included .gitkeep in a .quartoignore (otherwise these hidden .gitkeep files were not ignored!?) to prevent them from being copied.

When I quarto use template robert-koetsier/r-analysis in an empty directory only the _quarto.yml file is copied from the repo, no directories. Is there a way to include empty directories?

I'm using the Quarto CLI, v1.7.29, in git bash on windows 11.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the issue with quarto use template robert-koetsier/r-analysis and the repository containing _quarto.yml, .quartoignore, and .gitkeep files. Trace the quarto use template entry point to see how repository contents and ignored files are copied. Done means empty directories from the template are present without copying the ignored .gitkeep files.

Written by the indexing model from the issue text.

Assessment

Tech stack
git, github, javascript
Domain
cli
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.