← Back to issue list

GIt-LFS not pulled automatically

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#2054194
Type
issue
State
open
Author
~saviq
Labels
—
Created
Updated
Closed
—

Current evaluation

Feature request to automatically run `git lfs pull` for LFS-enabled `source-type: git` sources. Untriaged: no maintainer comments, labels, or reproducer. The git source plugin now lives in craft-parts, not snapcraft.

Suggested action: needs triage

Reason: The issue has zero maintainer comments, zero labels, no assignee, and no activity in 958 days, so it has never been assessed. AGENTS.md:18 assigns "Part lifecycle (pull, build, overlay, stage, prime) steps, plugins" to craft-parts, and `class Git`/`GitSource` have no matches in this repo, meaning GitSource.pull() is not implemented here — a maintainer must first decide whether to route this to craft-parts. The body is a single hedged suggestion ("It probably makes sense to...") with no reproducer, example project, or described workaround; a git-log search for "lfs" across both snapcraft and craft-parts found no prior attempt or partial fix. Main uncertainty is impact: LFS sources are a niche subset, so real demand is unproven until triaged.

Evaluated by: mr-cal-bot

Impact: 30 Quick Win: 4 Complexity: 50 Confidence: 82 Actionability: 25

Issue body

It probably makes sense to `git lfs pull` on lfs-enabled `source-type: git` sources.

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha
Impact: 30
Quick Win: 4
Complexity: 50
Confidence: 82
Actionability: 25
needs triage Feature request to automatically run `git lfs pull` for LFS-enabled `source-type: git` sources. Untriaged: no maintainer comments, labels, or reproducer. The git source plugin now lives in craft-parts, not snapcraft.
stealth/space-bunny-alpha
Impact: 42
Quick Win: 10
Complexity: 48
Confidence: 89
Actionability: 44
needs triage Automatic Git LFS downloads for Git sources are requested; current GitSource has no LFS handling, and the issue has no maintainer triage or reproduction.
qwen3.6-35b-a3b-mtp-q6
Impact: 50
Quick Win: 28
Staleness: 85
Complexity: 45
Confidence: 75
Support Request: 30
needs triage Feature request to automatically run git lfs pull for git sources; untriaged, no maintainer engagement after 929 days
qwen/qwen3.6-35b-a3b
Staleness: 95
Complexity: 15
Confidence: 80
Support Request: 10
close stale Suggests automatically running git lfs pull for git sources using LFS. Unlabelled, no maintainer response, inactive for over two years.
qwen/qwen3.6-35b-a3b
Staleness: 95
Complexity: 20
Confidence: 85
Support Request: 10
close stale Suggests automatically running git lfs pull for git-based sources. Unlabeled, zero maintainer interaction, and inactive for over two years.
qwen3.6-35b-a3b-mtp-q6
Staleness: 95
Complexity: 15
Confidence: 75
Support Request: 10
needs triage Suggests automatically running git lfs pull for git sources using LFS. Unlabelled, zero maintainer comments, and inactive for over two years.

Update history

Date Change
created

Related issues

No related issues found above the similarity threshold.