Repository navigation
Usage (Copier): specify git ref #413
Description
See ce6dd06: in Copier, if you want the most recent version of the template, you must specify so, otherwise it will by default search the git history for the latest tagged release.
So when #399 is merged, we should mention this in the README usage instructions. Also, we may want to release more often so that users that don't specify HEAD still get a recent version.
Activity
abelsiqueira commentedon Aug 6, 2024
I don't think we should encourage using
main, so I wouldn't add the instructions. I would focus on releasing often instead.sjvrijn commentedon Aug 6, 2024
We should at least include it in developer instructions for testing locally
abelsiqueira commentedon Aug 6, 2024
Agree. I'm actually working on that rn for Bestie
fdiblen commentedon Aug 22, 2024
related to #412
egpbos commentedon Aug 30, 2024
Just for context: this issue was discovered when testing the copier template dev version before it was released. Indeed, it fits better in the dev instructions. It was quite puzzling to see references to cookiecutter come up in error messages of the copier dev version, but the problem was that copier was referring back to 0.5.0 in the git history... which indeed was still the cookiecutter version :)