feat: Adding '--skip-answered' flag to enhance user interaction during copier update

[ljossha]

This Pull Request 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.

Issue: #1178

[codecov]

Codecov Report

Merging #1276 (8cdc16d) into master (a9e7b6b) will increase coverage by 0.16%.
Report is 25 commits behind head on master.
The diff coverage is 97.77%.

@@            Coverage Diff             @@
##           master    #1276      +/-   ##
==========================================
+ Coverage   96.95%   97.12%   +0.16%     
==========================================
  Files          47       48       +1     
  Lines        3969     4238     +269     
==========================================
+ Hits         3848     4116     +268     
- Misses        121      122       +1     

Flag	Coverage Δ
unittests	97.12% <97.77%> (+0.16%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files Changed	Coverage Δ
copier/main.py	95.99% <50.00%> (-0.09%)	⬇️
copier/cli.py	100.00% <100.00%> (ø)
tests/test_cli.py	100.00% <100.00%> (ø)
tests/test_prompt.py	93.87% <100.00%> (+2.44%)	⬆️

... and 8 files with indirect coverage changes

[yajo]

The code looks perfect to me. Just a minor non-blocking comment. Thanks for this contribution!

It seems you still have a little style issue... if you can run pre-commit it'll fix it for you.

[ljossha]

The code looks perfect to me. Just a minor non-blocking comment. Thanks for this contribution!

It seems you still have a little style issue... if you can run pre-commit it'll fix it for you.

I've fixed your suggested changes.
But when I try to run pre-commit, I receive:

An error has occurred: InvalidConfigError: 
=====> .pre-commit-config.yaml is not a file

Any ideas?

And another question: how long will it take to deploy in the brew after merging my changes?

UPD:
On running poe lint it returns:

[yajo]

You will have to run poe lint (as you did), and commit and push the changes.

Next release will still take some weeks. I don't want to release while on holidays. 🏖

[ljossha]

You will have to run poe lint (as you did), and commit and push the changes.

Next release will still take some weeks. I don't want to release while on holidays. 🏖

Yeah, I see. Pushed new changes.

[ljossha]

@yajo Hey man!
It seems that everything is fine.
Where will you be able to merge it?
Do you need anything from me at this point?

[yajo]

Since this is a new feature, I'd want to hand-test it before merge, so this will take a bit more than usual due to holidays. Maybe 1 or 2 weeks. But for now you can relax. According to the code, it seems perfect, so I'll just merge when I can give it a try. Otherwise I'll post what to change. Thanks!