copier update?

[34j]

Is your feature request related to a problem? Please describe.

I am a little frustrated that this repository is supposed to be a template, yet the content gets changed by your personal all-repos along with your other repositories.

Describe alternatives you've considered

• Add a CI that automatically opens PRs to follow updates easier ?
• Provide a way to subscribe your all-repos PRs ?
• (If you think this is a hassle then there would be no meaning using copier.)

Additional context

I have already created about 20~30 packages using this template and it is very tedious (and nearly impossible) to run copier update manually for each repository. Thanks in advance

Code of Conduct

• I agree to follow this project's Code of Conduct

Are you willing to resolve this issue by submitting a Pull Request?

• Yes, I have the time, and I know how to start.
• Yes, I have the time, but I don't know how to start. I would need guidance.
• No, I don't have the time, although I believe I could do it if I had the time...
• No, I don't have the time and I wouldn't even know how to start.

[abe-101]

@browniebroke recently brought Cruft to my attention.
It strive to solve the problem you mention.

I've only used it with Cookiecutter templates but i wonder if it
ll work with copier
or perhaps there's a similar tool for copier

[browniebroke]

I am a little frustrated that this repository is supposed to be a template, yet the content gets changed by your personal all-repos along with your other repositories.

It's a project template for -first and foremost- my own needs, and yes, I change a lot of stuff here as I change it into my other repos. I don't understand why changes made here with (or without) all-repos are preventing running copier update.

If you think this is a hassle then there would be no meaning using copier.

To add to my previous point, I don't really make use of copier update as a number of my repos were either created by hand or generated when this template was still a cookiecutter template (without copier). My intention with changing cookiecutter to copier was to make use of the update feature but I haven't got around to move to that fully yet, and by the sounds of it, it seems like it has some rough edges...

I have already created about 20~30 packages using this template and it is very tedious (and nearly impossible) to run copier update manually for each repository. Thanks in advance

The all-repos tool has a autofix_lib.run(...) which enables you to run any command on all your repos. I'm not sure whether it would work, but have you tried to run it with autofix_lib.run("copier", "update")?

All in all, this is a template for my own needs first and you're free to not use it. Happy to review ideas brought up by the community but at the end of the day, the decision to integrate a feature will come down to whether I'll use it myself. Sorry if this sounds selfish, but I don't intend to support every use case under the sun here.

[abe-101]

I just had a relativity easy time updating my project using uvx copier update --trust
mergecal/python-mergecal#107

The only caveat is i first changed some of the answers in .copier-answers.yml
specifically ones that are really only meant to be run at initial setup like:

initial_commit: false
setup_github: false
setup_pre_commit: false