Linter to warn if the summary field is over 78 characters
Metadata
Current evaluation
Requested summary-length warning remains unimplemented: summaries are capped at 200 characters, and no checker warns above 78; only an automated Jira-sync comment exists.
Suggested action: needs triage
Reason: The current CharmcraftSummaryStr permits 200 characters and explicitly cites #1598 as a future goal; linters.CHECKERS contains no summary checker. The request is precise, but the issue has no labels or substantive maintainer triage—the only comment is an automated Jira-sync notice—so it needs triage rather than closure.
Evaluated by: mr-cal-bot
Impact:
37
Quick Win:
24
Complexity:
25
Confidence:
94
Actionability:
88
Issue body
### What needs to get done
If the summary field is more than 78 characters long, warn the user during the linting process.
### Why it needs to get done
Charmcraft 3.0 introduces a summary length limit, but 78 broke too many charms. At a future point, we can revisit this limit and reduce it.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
37
Quick Win:
24
Complexity:
25
Confidence:
94
Actionability:
88
|
needs triage | Requested summary-length warning remains unimplemented: summaries are capped at 200 characters, and no checker warns above 78; only an automated Jira-sync comment exists. | |
| qwen/qwen3.6-35b-a3b |
Impact:
30
Quick Win:
16
Complexity:
25
Confidence:
70
Actionability:
70
|
keep open | Feature request to add a linter warning when charm summary exceeds 78 characters. Currently unimplemented; summary limit is 200 chars with a code comment referencing this issue as a future goal. | |
| qwen/qwen3.8-27b |
Impact:
35
Quick Win:
26
Staleness:
72
Complexity:
25
Confidence:
78
Support Request:
0
|
needs triage | Feature request to add a linter warning when charm summary exceeds 78 chars. Unimplemented; summary limit is currently 200 chars in project.py with a comment referencing this issue. No maintainer response beyond a bot Jira ticket sync. Last activity 381 days ago. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
85
Complexity:
20
Confidence:
75
Support Request:
10
|
needs triage | Feature request to add a linter warning when the metadata summary field exceeds 78 characters. Currently unlabelled and inactive for over a year, awaiting formal triage and prioritization. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
90
Complexity:
20
Confidence:
85
Support Request:
10
|
needs triage | Feature request to add a linter warning for summary fields exceeding 78 characters. Currently untriaged, inactive for over 10 months, with only a bot-generated Jira ticket comment. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
85
Complexity:
15
Confidence:
80
Support Request:
0
|
needs triage | Feature request to add a linter warning when the summary field exceeds 78 characters. Open since 2023 with no maintainer triage or implementation progress. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1440 summary field should be allowed more than 78 characters | charmcraft | closed | Closed as a duplicate of #1568, where the summary validation limit was raised from 78 to 200 characters; proposed PR #1585 was closed unmerged. |