Skip to content

Commit

Permalink
docs: add uses cases for updating a project (#1336)
Browse files Browse the repository at this point in the history
  • Loading branch information
ZhiliangWu authored Oct 1, 2023
1 parent bc1dfc0 commit f8614fc
Showing 1 changed file with 16 additions and 0 deletions.
16 changes: 16 additions & 0 deletions docs/updating.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,21 @@
# Updating a project

Copier enables the code lifecycle management for generated projects. There are several
common use cases for that, including but not limited to

1. Update the answers to previous questions

Questions can be reanswered to fit the latest requirements of the generated
projects. This is helpful, especially when the template includes optional tools that
fit into different phases of a project. In that case, template consumers are able to
activate the optional tools gradually when the project matures.

1. Sync updates from evolved templates

The template creators might update the template to add new functionalities or bug
fixes. The generated project can get updated if the template consumers want to keep
it to the latest version.

The best way to update a project from its template is when all of these conditions are
true:

Expand Down

0 comments on commit f8614fc

Please sign in to comment.