← 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 git sources; untriaged, no maintainer engagement after 929 days

Suggested action: needs triage

Reason: The issue has no labels, no maintainer comments, and has been inactive for 929 days without any assessment. A grep of craft-parts confirms no LFS-related code exists, so this feature request has never been addressed or evaluated.

Impact: 50 Quick Win: 27.5 Staleness: 85 Complexity: 45 Confidence: 75 Support Request: 30

Issue body

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

Evaluation history

Date Model Scores Action Summary
qwen3.6-35b-a3b-mtp-q6
Impact: 50
Quick Win: 27.5
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.
qwen3.6-35b-a3b-mtp-q6
Staleness: 95
Complexity: 20
Confidence: 80
Support Request: 10
needs triage Suggests automatically running git lfs pull for git sources using LFS. Unlabelled, zero maintainer comments, inactive for over two years.

Update history

No update history recorded yet.

Related issues

No related issues found above the similarity threshold.