`charmcraft init` should not populate actions.yaml with real data
Metadata
Current evaluation
charmcraft#197 was closed as abandoned after years of inactivity, with no recorded resolving PR or commit.
Resolution: closed stale
Reason: The issue remained inactive for over five years and was closed without a documented fix, resolving PR, commit, or maintainer explanation.
Evaluated by: mr-cal-bot
No scores available.
Issue body
After `charmcraft init` I notice that there is real YAML in `config.yaml` and `actions.yaml`.
While it would be OK to have examples in comments, having real YAML in there is likely to lead to someone uploading it to Charmhub without realising it.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed stale | charmcraft#197 was closed as abandoned after years of inactivity, with no recorded resolving PR or commit. | |
| stealth/space-bunny-alpha | — | closed stale | Abandoned: charmcraft init behavior was not changed; #197 was closed after years of inactivity with no resolving PR or commit. | |
| stealth/space-bunny-alpha | — | closed stale | Abandoned without a recorded fix: charmcraft#197 was closed after years of inactivity, with no resolving PR or commit. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed without resolution. The report that charmcraft init populates config.yaml and actions.yaml with real YAML, risking accidental Charmhub uploads, was abandoned due to inactivity. No fix was implemented. | |
| qwen/qwen3.6-35b-a3b | — | — | The request to prevent charmcraft init from populating actions.yaml with real YAML was closed without resolution or discussion. The feature request appears abandoned, leaving the default behavior unchanged. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution. The request to prevent charmcraft init from generating real YAML in actions.yaml and config.yaml was abandoned after five years with no comments or changes. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Requesting that charmcraft init avoid populating actions.yaml with real YAML was closed without resolution. No code changes were implemented, and the report was abandoned. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #35 charmcraft doesn't support actions | charmcraft | closed | Reported that charmcraft builds omitted actions.yaml, so charms with actions failed on install with 'CharmEvents' has no attribute. Fixed by merged PR #36 (commit a8cdb744), which makes 'charmcraft build' copy actions.yaml and config.yaml into the charm. | |
| #763 charmcraft V1.5.0 and V1.6.0 not bundling up bash actions | charmcraft | closed | Reported that charmcraft 1.5.0/1.6.0 omitted the charm's `actions` directory from built charms. Maintainer facundobatista closed it as a duplicate of #764, which was fixed by merged PR #768 (commit 5ada563c). | |
| #238 `charmcraft init` creates broken charm | charmcraft | closed | Superseded by charmcraft#247, a planned overhaul of init templates and generated tests; #247 later closed without implementing its proposed guard against building incomplete templates. | |
| #243 Initial tests from `charmcraft init` do not pass | charmcraft | closed | Superseded by charmcraft#247, which took ownership of redesigning charmcraft init and its generated tests; no direct fixing implementation was recorded for #243. |