← Back to issue list

cli: enable cleaning of parts

View original Github issue

Metadata

Project
snapcraft
Number
#2442
Type
pull request
State
merged
Author
sergiusens
Labels
Created
Updated
Closed

Current evaluation

Merged PR restoring snapcraft clean <part-name> functionality for build providers. Reviewers noted edge cases with dependent parts and suggested future improvements for VM-level cleanup, but the feature was successfully integrated.

Suggested action:

No scores available.

Issue body

Bring back snapcraft clean <part-name> when using build providers. LP: #1779136 Signed-off-by: Sergio Schvezov <sergio.schvezov@canonical.com> - [ ] Have you followed the [guidelines for contributing](https://github.com/snapcore/snapcraft/blob/master/CONTRIBUTING.md)? - [ ] Have you signed the [CLA](http://www.ubuntu.com/legal/contributors/)? - [ ] If this is a bugfix. Have you checked that there is a bug report open for the issue you are trying to fix on [bug reports](https://bugs.launchpad.net/snapcraft)? - [ ] If this is a new feature. Have you discussed the design on the [forum](https://forum.snapcraft.io)? - [ ] Have you successfully run `./runtests.sh static`? - [ ] Have you successfully run `./runtests.sh tests/unit`? -----

Evaluation history

Date Model Scores Action Summary
qwen/qwen3.6-35b-a3b Merged PR restoring snapcraft clean <part-name> functionality for build providers. Reviewers noted edge cases with dependent parts and suggested future improvements for VM-level cleanup, but the feature was successfully integrated.
qwen3.6-35b-a3b-mtp-q6 Merged. Restores the snapcraft clean command for build providers, enabling selective part cleanup. The update was accepted despite reviewer notes on dependent part edge cases and suggestions for VM-level cleaning enhancements.
qwen3.6-35b-a3b-mtp-q6 Restored snapcraft clean <part-name> functionality for build providers, addressing Launchpad bug #1779136. The pull request was merged despite a reviewer noting a dependency cleaning edge case.

Update history

No update history recorded yet.

Related issues

No related issues found above the similarity threshold.