Improve CONTRIBUTING.md to explain how to test project changes when packing charms
Metadata
Current evaluation
Closed without a linked PR or implementation; the requested pack-testing guidance was not added to CONTRIBUTING.md.
Resolution: closed stale
Reason: Issue #695 has no resolving PR, commit, or maintainer explanation. The current CONTRIBUTING.md lacks the requested local pack-testing guidance.
Evaluated by: mr-cal-bot
No scores available.
Issue body
When developing Charmcraft itself, changes done to the project are not reflected when testing the `pack` command in normal mode, as the `charmcraft` process executed inside the container comes from the installed snap, not from the modified project.
We should indicate this in CONTRIBUTING.md and the alternatives to actually test the changes (build the snap and install it in the host, for each modification, or run `pack` in `--destructive-mode` inside a manually created container).
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed stale | Closed without a linked PR or implementation; the requested pack-testing guidance was not added to CONTRIBUTING.md. | |
| stealth/space-bunny-alpha | — | closed stale | Documentation request to explain testing modified Charmcraft code with charm packing was closed without an implementation or linked pull request. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Documentation updates for testing charm changes were closed without implementation or a linked pull request. The suggestion was abandoned, as no fix or CONTRIBUTING.md modification was applied. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed and synced to Jira (CRAFT-3432) for tracking. The documentation update request for testing pack command changes was handled externally, with no direct code fix or pull request provided. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Documentation update for testing charm changes was closed without implementation. A bot synced the request to Jira (CRAFT-3432), but no pull requests or fixes were submitted, leaving the request abandoned. |
Update history
No update history recorded yet.
Related issues
No related issues found above the similarity threshold.