snapcraft close should complain early with one argument
Metadata
Current evaluation
Feature request for snapcraft close to validate arguments early, rejecting a single argument like 'edge/bump-20' and suggesting the correct command from snapcraft.yaml. Unlabeled, zero comments, inactive for nearly 8 years.
Suggested action: needs triage
Reason: The issue has no labels, no comments, and no maintainer interaction in nearly 8 years, so it has never been triaged. It is a valid UX improvement (early argument validation and a helpful error message) rather than a bug, but there is no evidence it was implemented or superseded, so it should be assessed by a maintainer rather than auto-closed.
Impact:
20
Quick Win:
14.0
Staleness:
95
Complexity:
30
Confidence:
60
Support Request:
20
Issue body
I find myself accidentally omitting the snap name quite often with snapcraft and didn't notice my mistake when attempting to close a branch using:
⟫ snapcraft close edge/bump-20
Your account lacks permission to close channels for this snap. Make sure the logged in account has upload permissions on 'edge/bump-20' in series '16'.
snapcraft knows that 'close' needs at least two arguments and additionally it should know that '/' is not a valid character for a snap name. By applying this knowledge, snapcraft could help me realise my typo.
Bonus points if it inspects the current directory for a snapcraft.yaml and suggests the right command to me.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.8-27b |
Impact:
20
Quick Win:
14.0
Staleness:
95
Complexity:
30
Confidence:
60
Support Request:
20
|
needs triage | Feature request for snapcraft close to validate arguments early, rejecting a single argument like 'edge/bump-20' and suggesting the correct command from snapcraft.yaml. Unlabeled, zero comments, inactive for nearly 8 years. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
15
Confidence:
85
Support Request:
0
|
close stale | Feature request to improve argument validation and error messaging for the snapcraft close command. Unlabeled, zero comments, inactive for nearly 8 years. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
10
Confidence:
90
Support Request:
0
|
close stale | Feature request to improve `snapcraft close` argument validation and error messaging. Issue is extremely stale with no maintainer interaction or updates over 8 years. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
98
Complexity:
15
Confidence:
85
Support Request:
5
|
close stale | Request to improve argument validation and error messaging for the snapcraft close command. Unlabelled, zero maintainer interaction, and inactive for nearly 8 years. | |
| qwen3.6-35b-moe-q4 |
Staleness:
95
Complexity:
20
Confidence:
85
Support Request:
10
|
close stale | Feature request to improve argument validation for snapcraft close, suggesting early error messages for missing snap names and optional snapcraft.yaml detection. Unaddressed for over 8 years. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1548915 snapcraft without argumens should just snap | snapcraft (launchpad) | closed | Closed without implementation. The feature request to run snapcraft without arguments was abandoned, with no discussion or code changes made. | |
| #1615764 Support snapcraft close | snapcraft (launchpad) | closed | The requested snapcraft close command was closed without implementation. It appears abandoned due to prolonged inactivity, with zero comments or development activity after opening. | |
| #1980155 snapcraft close example recommends non-existant flag | snapcraft (launchpad) | open | Help text example for 'snapcraft close' incorrectly includes --channel flag that doesn't exist. Issue is 4 years old with no activity for 2 years. | |
| #1699 snapcraft <help> command | snapcraft | closed | Closed without implementation or discussion. No resolution or merge details were provided, indicating the snapcraft help command feature request was abandoned. |