Issues:
In .copier-answers.yml, the current _commit is v0.3.2. The template is already linked to seedcase-project/t-squared, which is as of writing v0.10.0. Let's update the template 馃帀
What I tried:
I tried the included just update-from-template command, which runs. However, there are a number of files that seem to be updating towards seedcase-specific defaults, e.g.:
- next-steps.qmd repeatedly names Seedcase Project instead of rostools.
- CONTRINUTING.md references guidebook.seedcase-project
instead of guides.rostools
- the _quarto.yml layout
- the index.qmd welcome
- the README.md
- the 404 error (whether to use seedcase forest)
My question:
I've read the t-squared and template-workshop documentation but I'm not sure whether this is a problem of manually solving the merge conflicts in template-workshop the first time or whether this will repeat for future copier updates?
Maybe I'm confusing the source of the issue?
Issues:
In
.copier-answers.yml, the current _commit is v0.3.2. The template is already linked toseedcase-project/t-squared, which is as of writing v0.10.0. Let's update the template 馃帀What I tried:
I tried the included
just update-from-templatecommand, which runs. However, there are a number of files that seem to be updating towards seedcase-specific defaults, e.g.:instead of guides.rostools
My question:
I've read the t-squared and template-workshop documentation but I'm not sure whether this is a problem of manually solving the merge conflicts in template-workshop the first time or whether this will repeat for future copier updates?
Maybe I'm confusing the source of the issue?