Using (source-type: git; source: .) does not seem to ever realise files have changed, snap rebuild caches code changes
Metadata
Current evaluation
Snapcraft with source-type: git and source: . never detects local file changes, reusing cached source instead of re-pulling. Maintainer confirmed behavior is incorrect but suggested using source-type: local as workaround. Issue is 794 days old with no fix.
Suggested action: keep open
Reason: Maintainer @lengau explicitly acknowledged the behavior is incorrect ('this behaviour is still incorrect') while suggesting source-type: local as a workaround. The issue is a genuine bug in craft-parts' GitSource where local git sources don't track file changes. The GitSource._pull_existing() method uses git fetch/reset which won't detect uncommitted local changes, and the checksum mechanism likely doesn't account for working tree modifications. This is a real bug affecting developers using local git sources, though the workaround (source-type: local) mitigates it. The issue is stale (794 days, last activity 776 days ago) but the underlying bug in craft-parts GitSource appears to still exist based on current code inspection.
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.8-27b |
Impact:
55
Quick Win:
33.0
Staleness:
75
Complexity:
40
Confidence:
70
Support Request:
10
|
keep open | Snapcraft with source-type: git and source: . never detects local file changes, reusing cached source instead of re-pulling. Maintainer confirmed behavior is incorrect but suggested using source-type: local as workaround. Issue is 794 days old with no fix. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
85
Complexity:
50
Confidence:
75
Support Request:
10
|
needs triage | Unlabelled bug report detailing snapcraft caching issues with source-type: git and source: . Requires maintainer assessment to verify current behavior and assign priority. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
85
Complexity:
65
Confidence:
80
Support Request:
10
|
close stale | Snapcraft fails to detect source changes when using source-type: git with source: ., causing cached builds to ignore local modifications. Issue has been inactive for over a year with a maintainer-provided workaround. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
40
Confidence:
70
Support Request:
10
|
close stale | Bug where source-type git with source dot incorrectly caches local changes, skipping rebuilds. Maintainer acknowledges the flaw and suggests source-type local as a workaround. Issue remains open, unlabeled, and awaiting triage. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1860526 source-type breaks remote-build | snapcraft (launchpad) | open | snapcraft remote-build fails when source-type is git because the source directory differs from the working directory, causing go dep to fail. The remote-build command has since been removed from snapcraft, making this issue obsolete. |