`snapcraft --shell` shouldn't run the lifecycle steps
Metadata
Current evaluation
Bare snapcraft --shell runs lifecycle actions before opening the shell. The one-line reproducer is confirmed, but the default snap command semantics and a definitive resolution are not documented.
Suggested action: keep open
Reason: Keep it open: the report gives the exact invocation and expected/current behavior, and the reporter later said they had reproduced it. The current lifecycle code converts shell into running the previous step, while the maintainer's final comment identifies the default snap command as the complication; no resolving commit, release, or verified current behavior is cited.
Evaluated by: mr-cal-bot
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
43
Quick Win:
13
Complexity:
58
Confidence:
84
Actionability:
72
|
keep open | Bare snapcraft --shell runs lifecycle actions before opening the shell. The one-line reproducer is confirmed, but the default snap command semantics and a definitive resolution are not documented. | |
| stealth/space-bunny-alpha |
Impact:
25
Quick Win:
8
Complexity:
40
Confidence:
88
Actionability:
50
|
close not a bug | Bare `snapcraft --shell` runs predecessor steps for the default `snap` command; evidence indicates this is intended step-scoped behavior, not a lifecycle-skipping option. | |
| stealth/space-bunny-alpha |
Impact:
42
Quick Win:
13
Complexity:
55
Confidence:
84
Actionability:
67
|
keep open | Bare snapcraft --shell unexpectedly runs all non-pack lifecycle steps before opening the build environment; the behavior remains unresolved after maintainers identified default snap command ambiguity. | |
| stealth/space-bunny-alpha |
Impact:
45
Quick Win:
16
Complexity:
45
Confidence:
74
Actionability:
63
|
needs triage | `snapcraft --shell` unexpectedly runs all lifecycle steps except `pack`; the report expects an immediate build-environment shell, but it lacks labels or maintainer triage. | |
| qwen/qwen3.8-27b |
Impact:
15
Quick Win:
11
Staleness:
95
Complexity:
25
Confidence:
60
Support Request:
10
|
close stale | Bug report claiming `snapcraft --shell` runs lifecycle steps instead of dropping into the build environment shell. 7+ years old, 0 comments, no labels; the `--shell` flag was removed in the modern CLI and `snapcraft shell` now provides the requested behavior. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
15
Confidence:
85
Support Request:
5
|
close stale | Bug report claiming `snapcraft --shell` runs lifecycle steps instead of dropping into a shell. The issue is over 7 years old with zero comments or maintainer interaction. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
25
Confidence:
90
Support Request:
5
|
close stale | snapcraft --shell unexpectedly executes lifecycle steps instead of immediately dropping into a build environment shell. Untriaged, inactive for over 7 years. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
98
Complexity:
25
Confidence:
80
Support Request:
5
|
close stale | `snapcraft --shell` runs lifecycle steps instead of dropping into a build shell. The report is over 7 years old, has no maintainer interaction, and likely reflects obsolete behavior given major CLI and lifecycle changes in recent snapcraft versions. |
Update history
| Date | Change |
|---|---|
| created |
Related work
-
Related To:
snapcraft (launchpad)#1782768
(confidence 95%)
Explicitly related feature issue about adding --shell to lifecycle steps, covering the same CLI capability and intended step semantics.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1782767 Add --shell-after for lifecycle steps | snapcraft (launchpad) | closed | Implemented --shell-after via merged snapcore/snapcraft PR #2253 (commit 21cfd4750), opening a shell after the selected lifecycle step. | |
| #1782768 Add --shell for lifecycle steps | snapcraft (launchpad) | closed | Feature request closed by the author's own pointer to snapcraft PR #2254, which added --shell support to build providers (commit a24d398e4); companion --shell-after landed in PR #2253. |