`--force` Considered Harmful™
Metadata
Current evaluation
Charmcraft still exposes ambiguous --force flags; descriptive replacements, hidden legacy flags, and usage warnings requested by maintainer remain unimplemented.
Suggested action: keep open
Reason: The current checkout still defines --force in lifecycle.py, init.py, and analyse.py, with no --override-linters implementation, so the requested work is not resolved. The maintainer explicitly asked for CLI naming guidance and an internal ticket, CRAFT-2525, was created; the remaining ambiguity is which descriptive names and warning behavior to adopt, not whether the issue is valid.
Evaluated by: mr-cal-bot
Impact:
45
Quick Win:
16
Complexity:
50
Confidence:
91
Actionability:
72
Issue body
### What needs to get done
Replace all `--force` command line options with more descriptive parameters. Suppress `--force` from the help text and warn the user against its usage when used (though still allow its use for now).
For example in the `pack` command, `--force` should be replaced with `--override-linters`
### Why it needs to get done
`--force` Considered Harmful™
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
45
Quick Win:
16
Complexity:
50
Confidence:
91
Actionability:
72
|
keep open | Charmcraft still exposes ambiguous --force flags; descriptive replacements, hidden legacy flags, and usage warnings requested by maintainer remain unimplemented. | |
| qwen/qwen3.6-35b-a3b |
Impact:
30
Quick Win:
13
Complexity:
40
Confidence:
75
Actionability:
70
|
needs triage | Replace --force CLI options with descriptive alternatives across charmcraft commands (pack, analyse, init). Still open, unlabelled, last active 398 days ago. | |
| qwen/qwen3.8-27b |
Impact:
30
Quick Win:
18
Staleness:
55
Complexity:
40
Confidence:
75
Support Request:
5
|
needs triage | Feature request to replace the ambiguous --force CLI option in charmcraft commands (pack, init, analyse) with descriptive parameters like --override-linters, suppress it from help, and warn on use. Still unimplemented in current code; no labels, no assignee, awaiting maintainer decision on CLI guidelines. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
75
Complexity:
30
Confidence:
70
Support Request:
0
|
needs triage | Feature request to replace generic --force CLI flags with descriptive alternatives. Unlabelled, unassigned, and inactive for over a year pending maintainer guidance on CLI guidelines. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
85
Complexity:
45
Confidence:
70
Support Request:
10
|
needs triage | Proposes replacing generic --force CLI flags with descriptive alternatives across commands. Currently unlabelled and awaiting CLI design guidelines after a maintainer inquiry 10 months ago. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
85
Complexity:
45
Confidence:
80
Support Request:
5
|
needs triage | Proposes replacing all --force CLI flags with descriptive alternatives, suppressing them from help, and adding warnings. Currently awaiting CLI design guidelines and maintainer action. |
Update history
No update history recorded yet.
Related issues
No related issues found above the similarity threshold.