-
-
Notifications
You must be signed in to change notification settings - Fork 182
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Don't require users to review all questions when running copier update #1178
Comments
I like the idea. 👍 I'd use a flag though, e.g. |
Using |
At the end of the day, it would just be nice not to be forced to review all the prior responses when updating :) |
Maybe, but I don't have plans to implement this, but any PR would be welcome. |
This change addresses a usability issue troubling users when they run 'copier update'. Previously, each time 'copier update' was run, the user had to review all responses given in the answers file. This was a repetitive and laborious process, particularly for users dealing with extensive templates. This PR introduces a new flag --skip-answered to improve the user experience and reduce friction during updates. The new flag allows users to bypass the review of questions already answered in the past. It automatically pulls responses from the answers file and presents only the newly added template questions to the user for their review. `skip-answered` will skip all answered questions and ask user input only for new inputs if they are present. Fixes #1178 Co-authored-by: Jairo Llopis <[email protected]>
Actual Situation
When someone runs
copier update
, they have to review all of the responses that they have provided in their answers file. People get kind of blind to these responses and just return through the list as fast as possible.Desired Situation
It would be nice if there was an argument that would take all the previous responses found in the answers file and only present the user with new template questions that were added after the hydrated project was created.
Proposed solution
I have no technical solution, but an initial questions like this would be amazing. (Actual wording should be improved.)
The text was updated successfully, but these errors were encountered: