Opt out of adding git as a build-package
Metadata
Current evaluation
Feature request to allow opting out of git as a build-package when craft.git binary is present. Depends on #900 (closed without implementation), but related PR #925 already merged craft.git preference. No maintainer activity in ~18 months, unlabelled.
Suggested action: needs triage
Reason: The issue is unlabelled with no maintainer response beyond the Jira sync bot, and its explicit dependency (#900) was closed without implementation. However, PR #925 ("feat: use craft.git for git where possible") was merged and implemented the core craft.git preference that #900 sought, while the actual opt-out mechanism in _get_build_packages/get_packages_for_source_type remains unimplemented. A maintainer needs to assess whether #925 effectively unblocks this work and decide on an opt-out approach.
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.8-27b |
Impact:
40
Quick Win:
22.0
Staleness:
72
Complexity:
45
Confidence:
72
Support Request:
10
|
needs triage | Feature request to allow opting out of git as a build-package when craft.git binary is present. Depends on #900 (closed without implementation), but related PR #925 already merged craft.git preference. No maintainer activity in ~18 months, unlabelled. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
90
Complexity:
30
Confidence:
75
Support Request:
10
|
close stale | Feature request to allow opting out of adding git as a build-package if craft.git exists. Currently blocked by upstream issue #900 and has seen no maintainer activity or progress in over 16 months. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
85
Complexity:
30
Confidence:
90
Support Request:
10
|
needs triage | Feature request to allow opting out of git as a build-package. Over a year old, unlabelled, and lacks maintainer assessment or assignee, awaiting initial triage. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
20
Confidence:
80
Support Request:
0
|
close stale | Allow opting out of adding git as a build-package when craft.git is configured. Needed for future bases to exclude git. Currently open, depends on craft-parts issue 900, synced to Jira CRAFT-3763. Last activity 465 days ago. |
Update history
No update history recorded yet.
Related work
-
Blocked By:
canonical/craft-parts#900
(confidence 85%)
Issue body explicitly states 'Depends on canonical/craft-parts#900'. That issue was closed without implementation or resolution, described as abandoned.
-
Related To:
canonical/craft-parts#925
(confidence 80%)
PR #925 added craft_parts/utils/git.py with get_git_command() preferring the craft.git binary, implementing the core of what #900 requested, but did not add the build-package opt-out mechanism this issue asks for.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #900 use `craft.git` for git operation instead of relying on build-package | craft-parts | closed | Closed without implementation. The craftgit migration was abandoned and tracked internally via Jira ticket CRAFT-3664, with no pull request or code changes submitted. |