fix: use Git CLI for Cargo dependencies - #26
Merged
Conversation
danielkov
enabled auto-merge (squash)
August 26, 2026 15:14
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Configure Cargo to fetch Git dependencies through the system Git CLI instead of its embedded Git transport.
Motivation
Some contributors rewrite GitHub HTTPS URLs to SSH and rely on SSH configuration that Cargo's embedded transport cannot use. Delegating Git fetches to the system client lets Cargo use their existing SSH configuration and credential helpers, preventing authenticated Git dependencies from blocking
cargo build --locked.Impact
This affects dependency fetching during builds only. Runtime behavior is unchanged.