← Back to issue list

snapcraft close example recommends non-existant flag

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#1980155
Type
issue
State
open
Author
~jameinel
Labels
Created
Updated
Closed

Current evaluation

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.

Suggested action: close stale

Reason: The issue is 1527 days old with no maintainer engagement for 778 days. The fix is trivial (removing --channel from the help example), and the lack of activity over 2 years suggests the issue is no longer a priority. The project has likely evolved significantly in 4 years.

Impact: 10 Quick Win: 9.5 Staleness: 85 Complexity: 5 Confidence: 55 Support Request: 0

Issue body

Running `snapcraft close help` it gives this example: $ snapcraft close --help Usage: snapcraft close [options] <name> <channel> ... Examples: snapcraft close my-snap --channel beta However, it does not support a `--channel` flag, and the example is incorrect. Following the example gives a failure: $ snapcraft close juju --channel 2.4/stable Usage: snapcraft [options] command [args]... Try 'snapcraft close -h' for help. Error: unrecognized arguments: --channel $ snapcraft --version snapcraft 7.0.7 (all it really needs is to remove the `--channel` from the example command)

Evaluation history

Date Model Scores Action Summary
qwen3.6-35b-a3b-mtp-q6
Impact: 10
Quick Win: 9.5
Staleness: 85
Complexity: 5
Confidence: 55
Support Request: 0
close stale 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.
qwen/qwen3.6-35b-a3b
Staleness: 95
Complexity: 5
Confidence: 75
Support Request: 10
needs triage Documentation example for snapcraft close incorrectly includes a non-existent --channel flag, causing command failures. Unlabelled and unacknowledged by maintainers.
qwen/qwen3.6-35b-a3b
Staleness: 95
Complexity: 5
Confidence: 90
Support Request: 0
needs triage Reports incorrect --channel flag in snapcraft close help example. Unlabeled, no maintainer response, inactive for over two years.
qwen3.6-35b-a3b-mtp-q6
Staleness: 95
Complexity: 5
Confidence: 85
Support Request: 10
needs triage Reports incorrect --channel flag in snapcraft close help example. Issue is unlabelled, has no maintainer comments, and is over 4 years old.
qwen3.6-35b-a3b-mtp-q6
Staleness: 95
Complexity: 5
Confidence: 85
Support Request: 5
close stale Documentation example for snapcraft close incorrectly includes a --channel flag that is not supported, causing command failures. Issue remains untriaged and inactive for over two years.

Update history

No update history recorded yet.

Related work

  • Related To: launchpad#1735800 (confidence 70%)

    Related issue about snapcraft close command behavior, though this is about a different aspect (argument handling vs help text)

Related issues

Issue Project State Summary Similarity
#1735800 snapcraft close should complain early with one argument snapcraft (launchpad) open 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.
71%