-
-
Notifications
You must be signed in to change notification settings - Fork 186
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
Suggested improvements to the update process #877
Comments
Indeed it can be counter-intuitive, but this "overwrite" does not mean you lose your local changes, as they will be re-applied after the local files have been updated. I believe all these (valid) points are covered by the plans @yajo already has, namely to entirely remove this "overwrite prompt" feature, and to allow finer-grained execution of tasks. |
Ok, great news, thanks for that. There is probably also a way to avoid this double execution of a lot of the workload that happens during an update - but great to know something is in development - are there any more details on what is expected and when? Just to manage my expectations and excitement! Loving copier so far. Thanks |
You can follow the task issue here: #240. |
Thanks @pawamoy, I'll do that and I'll close this issue, thank you. |
Well, #807 is a bit a different story. It's about having inline merge conflict markers. However it paves the way to not need overwrite prompts anymore too. I maintain Copier in my free time. I try to commit some hours to it like about once every 2 weeks. Right now I'm focused on finishing #585 before the next release. But as you can guess, there's no real schedule. Help is always appreciated! |
Unless I am misunderstanding the intended use of the update process, I think that there might be 3 missing features which would really improve the update experience:
Thanks for the consideration / your time in responding to these.
The text was updated successfully, but these errors were encountered: