While the _copier_conf.operation variable is not yet available (hopefully soon), we could differentiate updates from copies using a ContextHook that checks for the presence of .copier-answers.yml, but waiting makes more sense (being able to use RenovateBot depends on the same variable).
We can just rely on the new migration syntax in 9.3.0.
After copying, the user needs to:
main
as the default branch)python -m pip install -e '.[dev,tests,docs]'
pre-commit run -a
, at least twiceAfter updating, the user needs to:
pre-commit run -a
, sometimes twiceBoth should be automated, especially if we want RenovateBot auto-updates to work more reliably.
The task should probably be written in Python to be more robust. For inspiration, see https://github.com/salt-extensions/salt-extension-migrate (
plumbum
should be available in the Copier venv, need to double-check).While the_copier_conf.operation
variable is not yet available (hopefully soon), we could differentiate updates from copies using a ContextHook that checks for the presence of.copier-answers.yml
, but waiting makes more sense (being able to use RenovateBot depends on the same variable).We can just rely on the new migration syntax in
9.3.0
.