Automated (partial) update for generated projects

[apirogov]

This could prove difficult to provide in a useful way, but it would be great if repositories based on this template have some mechanism to:

• check whether a new version of the template is available
• create a PR suggesting changes reflecting the new template

It could work similarly to e.g. carpentries/workbench-template-md (instantiated e.g. here)

At least for the CI scripts and certain non-templated configuration files this might be both realistic and convenient, simplifying project maintenance.

Still, this needs some more thinking and discussions to clarify what and how and with how much effort could and should be updated in a semi-automated fashion.

[apirogov]

After further thinking it feels like rather difficult and infeasible.

Carpentries projects are much more homogeneous, by design. This template is supposed to be used in various ways and adapted in unexpected places. Such a feature would require a lot of effort with unclear benefit.

Alternative idea:

When initializing project, ask if the user wants to know about new versions of the template.

If confirmed, add/activate some CI script that would create an issue for the project like "check out the new template" and points to the changelog.

This might be the least invasive and pragmatic way to nudge users to keep their repo structure up to date. However, it is unclear if anyone would be interested in using such a thing.

[apirogov]

This could be useful https://github.com/cruft/cruft/