feat(metadata): add charm-user to charmcraft.yaml
Metadata
Current evaluation
Merged a feature adding charm-user to charmcraft.yaml, resolving issue #1806. Approved by two reviewers and passing CI, the update modifies five files with 38 additions and 2 deletions.
Suggested action: —
No scores available.
Issue body
Fixes #1806
CRAFT-3211
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Merged a feature adding charm-user to charmcraft.yaml, resolving issue #1806. Approved by two reviewers and passing CI, the update modifies five files with 38 additions and 2 deletions. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Added charm-user to charmcraft.yaml, resolving issue #1806 and addressing CRAFT-3211. The change was merged by maintainer lengau. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Merged by maintainer lengau, this change resolves issue #1806 and CRAFT-3211 by adding the charm-user field to charmcraft.yaml. The update was accepted and integrated without additional review comments. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #397 feat: add charmcraft inspector | fetch-service | merged | Merged the charmcraft inspector, verifying charmcraft.yaml existence. Approved by two reviewers, passed CI, and changed 7 files. The author addressed invocation order review comments prior to final merge. | |
| #46 New functionality from charmcraft (CRAFT-706). | craft-cli | merged | Merged new charmcraft functionality (CRAFT-706) following approval from two reviewers. The update adds approximately 2000 lines across 13 files, successfully integrating the feature set into the codebase. | |
| #1974 Check `charmcraft.yaml` for charm name | charmcraft | merged | Merged changes to validate the charm name in charmcraft.yaml, resolving issue 1973. It passed CI, received two approvals, and was merged after the author corrected a CLA email mismatch via force push. | |
| #1149 command: charmcraft init to use charmcraft.yaml only | charmcraft | merged | Merged after review. Updated charmcraft init to use a unified charmcraft.yaml by default, replacing separate metadata, actions, and config files. Added profile descriptions and updated URLs. Initially blocked but eventually merged. | |
| #471 config: add charm part to documentation (CRAFT-356) | charmcraft | merged | Merged changes adding charm configuration documentation to the configuration schema. Approved by two reviewers with zero unresolved comments. Updated two files with 15 additions and one deletion. Resolves CRAFT-356. | |
| #2195 docs: add `charm-user` in the charmcraft.yaml file reference | charmcraft | merged | Merged documentation update adding the charm-user field to the charmcraft.yaml reference. The contributor also added the field to a basic smoke test for e2e coverage. Commits will be squashed upon merge. | |
| #1126 Allow use actions/config/metadata in charmcraft.yaml | charmcraft | merged | Merged. Allows defining actions, config, and metadata directly in charmcraft.yaml when corresponding files are absent. Addresses CRAFT-1747, CRAFT-1788, and CRAFT-1789. Approved with passing CI checks. | |
| #31 feat: charmcraft actions | craft-actions | merged | Merged changes adding two GitHub Actions: charmcraft/setup installs Charmcraft and LXD, while charmcraft/pack builds charms. Approved by two reviewers with passing CI checks, the update adds 299 lines across six files to streamline workflows. | |
| #1622 fix: reorganise charmcraft.yaml preprocessing | charmcraft | merged | Merged following two approvals and passing CI. Reorganized charmcraft.yaml preprocessing to apply extensions on raw data, assign default parts to charms with bases, and enforce dictionary type for parts. Modified 5 files (+27/-14 lines). | |
| #2589 docs: add Charmcraft 4.2 release notes | charmcraft | merged | Merged pull request adding Charmcraft 4.2 release notes. The update adds 113 lines across two documentation files. Changes were reviewed, approved, and successfully integrated into the main branch. |