Skip to content

Better way to handle template updates #26

Description

@seveneleven

Is your feature request related to a problem? Please describe.
For commands, that incorporate a template repository (moryx new, moryx add, etc.), you have to add --pull in order to use the latest version of the template.

Describe the solution you'd like
After running a command, the CLI should raise a 'warning', that it run on an outdated version or that a newer version is available.

Describe alternatives you've considered
I always assumed that updating automatically was to intrusive. But that could be an option, too. It's maybe even expected. For example, if I use --branch v1 I probably always want the latest version of v1 including all updates, whereas I would explicitly use --branch v1.2 in case I didn't want latest v1.4

Acceptance criteria
n/a

Related issues/discussions
n/a

Additional context
n/a

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Fields

No fields configured for Feature.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions