Skip to content

Automated 'new template version' PR should use copier's new template version checker #59

Description

@irm-codebase

Is your feature request related to a problem? Please describe.
We currently rely on the latest tag to check for template updates in the template's YAML.

_commit: latest

This was added because copier (at the time) did not support template version checks.
This was added recently, so there is no longer a need for it.

Describe the solution you'd like

  • Reliance on latest should be depreciated in favour of keeping the template's version.
    This would make .copier_answers.yml more useful, as it now would show the specific template version used in _commit:
  • The README.md should instruct users to use the latest version explicitly (this should be automated / tested so we do not need to manually update it).

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
PR with the new feature: copier-org/copier#2463

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions