Automatically update template operator based on latest charmcraft init
Metadata
Current evaluation
Rejected and closed. Maintainer declined automatic template updates due to upcoming charmcraft init profiles, potential divergence, and policy against cross-repo automation. May revisit once profiles are widely adopted.
Suggested action: —
No scores available.
Issue body
There is a GitHub repo (https://github.com/canonical/template-operator) used as a template for many teams when starting new charms. For any changes to the default/ recommended starting point of charms, both the `charmcraft init` command and the template-operator repo have to be updated. This could potentially be improved by unifying the two, for example by include a GitHub action on this repository to automatically send a commit to the template-operator based on the latest output of `charmcraft init`.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen3.6-35b-a3b-mtp-q6 | — | — | Rejected and closed. Maintainer declined automatic template updates due to upcoming charmcraft init profiles, potential divergence, and policy against cross-repo automation. May revisit once profiles are widely adopted. | |
| qwen/qwen3.6-35b-a3b | — | — | Rejected. Maintainers declined automating updates between charmcraft init and template-operator due to upcoming init profiles, architectural divergence, and cross-repo automation policies. The idea may be revisited later. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Rejected and closed. Maintainer declined automating sync between charmcraft init and template-operator due to upcoming charmcraft profiles, architectural divergence, and cross-repo automation policy. May revisit later. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Rejected and closed. Maintainers declined automating sync between charmcraft init and template-operator, citing upcoming profiles support that will redefine template management. The proposal may be revisited later. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #762 Dynamically import charmcraft init template | charmcraft | closed | Closed as superseded by broader init profiles work. Dynamic template fetching was deferred to avoid internet dependency. Template customization will instead rely on vendored profiles and init-time substitutions. | |
| #2793 Update init templates to use a single current Charmcraft docs link | charmcraft | closed | Rejected and closed without merging. A maintainer noted the template cleanup contradicted previous requests, as it removed legacy documentation comments instead of consolidating them as intended. |