Include/exclude patterns improvements
Metadata
Current evaluation
Requests stage/prime include/exclude precedence changes; remains open and untriaged after 3233 days, with lifecycle handling now delegated to craft-parts.
Suggested action: needs triage
Reason: The body identifies the current exclude-wins behavior but provides no concrete manifest or reproducer and leaves two incompatible precedence rules to choose from, requiring design triage. The metadata shows no labels and zero comments, while PartsLifecycle now delegates part behavior to craft_parts, so implementation ownership and any existing upstream resolution should first be established.
Evaluated by: mr-cal-bot
Impact:
35
Quick Win:
5
Complexity:
68
Confidence:
84
Actionability:
43
Issue body
Hi,
(This was actually mentioned by a customer and I'm forwarding on their behalf.)
When listing files to stage or prime for a part in snapcraft.yaml, the list of patterns seems to be sorte into an include list and an exclude list, and then processed in a way where all excludes win over all includes.
Instead, it might be more useful to either always process all includes last, or to process includes/excludes in the order specified in the snapcraft.yaml. This would allow handling a broader variety of cases.
Best,
- Loïc
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
35
Quick Win:
5
Complexity:
68
Confidence:
84
Actionability:
43
|
needs triage | Requests stage/prime include/exclude precedence changes; remains open and untriaged after 3233 days, with lifecycle handling now delegated to craft-parts. | |
| qwen/qwen3.6-35b-a3b |
Impact:
30
Quick Win:
5
Complexity:
40
Confidence:
60
Actionability:
30
|
needs triage | Feature request to improve include/exclude pattern ordering in snapcraft.yaml filesets for staging/priming | |
| qwen/qwen3.8-27b |
Impact:
40
Quick Win:
18
Staleness:
95
Complexity:
55
Confidence:
70
Support Request:
15
|
needs triage | Feature request for snapcraft parts: include/exclude file patterns are processed with all excludes winning over all includes; reporter wants includes processed last or in yaml order to support more cases. No maintainer response, no labels, 0 comments, ~8.8 years old. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
30
Confidence:
85
Support Request:
5
|
needs triage | Suggestion to reorder include/exclude pattern processing in snapcraft.yaml. Unlabelled, unassigned, and has received no maintainer comments in over 8 years. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
50
Confidence:
85
Support Request:
10
|
needs triage | Feature request to change include/exclude pattern processing order in snapcraft.yaml. Suggests processing includes last or preserving specified order instead of excludes overriding includes. Unlabeled, zero comments, inactive for ~8.5 years, awaiting maintainer assessment. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
98
Complexity:
55
Confidence:
90
Support Request:
25
|
close stale | Suggests changing snapcraft.yaml include/exclude pattern processing order so includes can override excludes or follow specified order. Issue has been inactive for nearly 9 years with zero maintainer interaction. |
Update history
| Date | Change |
|---|---|
| created |
Related issues
No related issues found above the similarity threshold.