← Back to issue list

Reorganise sample charm documentation to include the most common keys at the top.

View original Github issue

Metadata

Project
charmcraft
Number
#2643
Type
issue
State
open
Author
lengau
Labels
Status: Triaged Type: Documentation
Created
Updated
Closed
—

Current evaluation

Maintainer request to reorder the sample charmcraft.yaml so required keys (name, base, parts) appear first, and align the reference docs. Triaged; sample file currently starts with actions and ends with type.

Suggested action: keep open

Reason: The issue is labelled 'Status: Triaged' and 'Type: Documentation', was filed by a maintainer, and points to a specific file (docs/reference/files/charmcraft-sample-charm.yaml) plus a linked PR review comment. Repository inspection confirms the sample YAML currently begins with 'actions:' and places 'type: charm' at the very bottom, so the requested reordering is a valid, clearly scoped documentation improvement that remains open.

Evaluated by: mr-cal-bot

Impact: 30 Quick Win: 17 Complexity: 30 Confidence: 75 Actionability: 80

Issue body

### Check existing issues - [x] I've verified that this request isn't described by any existing issues. ### Request See: https://github.com/canonical/charmcraft/pull/2632/changes#r3030066362 Reorganise the sample charm so required keys (name, base, parts, etc.) are at the top. Probably also reorganise the documentation to match. ### Document location https://documentation.ubuntu.com/charmcraft/stable/reference/files/charmcraft-yaml-file/

Evaluation history

Date Model Scores Action Summary
~deepseek/deepseek-pro-latest
Impact: 30
Quick Win: 17
Complexity: 30
Confidence: 75
Actionability: 80
keep open Maintainer request to reorder the sample charmcraft.yaml so required keys (name, base, parts) appear first, and align the reference docs. Triaged; sample file currently starts with actions and ends with type.
qwen/qwen3.6-35b-a3b
Impact: 30
Quick Win: 19
Complexity: 10
Confidence: 80
Actionability: 70
keep open Reorganize sample charm documentation to place required keys (name, base, parts) at the top. Triaged documentation improvement, open for 163 days with no follow-up.
qwen/qwen3.8-27b
Impact: 20
Quick Win: 17
Staleness: 55
Complexity: 15
Confidence: 70
Support Request: 0
keep open Documentation improvement: reorganise sample charm YAML and reference docs so required/common keys (name, base, parts) appear first instead of alphabetically. Triaged by maintainer, no implementation yet; sample file still alphabetical.
qwen3.6-35b-a3b-mtp-q6
Staleness: 45
Complexity: 15
Confidence: 85
Support Request: 0
keep open Documentation request to reorder sample charm YAML keys, placing required fields like name and base at the top. Triaged and awaiting implementation.
qwen3.6-35b-a3b-mtp-q6
Staleness: 60
Complexity: 15
Confidence: 85
Support Request: 0
keep open Request to reorder sample charm documentation so required keys like name, base, and parts appear first, aligning with reference docs. Currently triaged but inactive for 91 days.
qwen3.6-35b-a3b-mtp-q6
Staleness: 55
Complexity: 10
Confidence: 85
Support Request: 0
keep open Documentation task to reorder sample charm YAML keys to place required fields at the top, aligning with PR feedback. Currently triaged but inactive for 88 days.

Update history

No update history recorded yet.

Related work

  • Related To: canonical/charmcraft#2632 (confidence 80%)

    The issue was raised from a review comment on PR #2632 (docs: update docs to use 26.04 as the generic base), which is merged but does not implement this reorganisation.

Related issues

No related issues found above the similarity threshold.