Move Git abstraction outside of remotebuild
Metadata
Current evaluation
Closed and superseded by internal Jira ticket CRAFT-3123. No public implementation or merge details provided. The request to extract git handling into a separate module remains unaddressed.
Suggested action: —
No scores available.
Issue body
### What needs to get done
Create a separate module for handling git repositories.
Move the code related to git repository handling from `remotebuild` to the new `git` module.
### Why it needs to get done
Currently Git repository handling is a part of `remotebuild` module.
There is a need for a common place for abstraction around git repository handling, that may be reused in different places.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Closed and superseded by internal Jira ticket CRAFT-3123. No public implementation or merge details provided. The request to extract git handling into a separate module remains unaddressed. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed and superseded by internal Jira ticket CRAFT-3123. No pull requests or code changes were created to extract the git handling module from remotebuild. The request remains unimplemented. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Extracting Git handling into a separate module was closed without implementation. No pull request or resolution was provided, indicating the task was abandoned or deferred to internal Jira tracking. |
Update history
No update history recorded yet.
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. |