Expand ~ in user.signingKey for SSH signing#158
Open
simono wants to merge 1 commit into
Open
Conversation
Python's open() and ssh-keygen -f do not expand tilde, so a signingKey value like ~/.ssh/id_ed25519.pub would fail with a file-not-found error. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
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.
Python's
open()andssh-keygen -fdo not expand tilde, so auser.signingKeyvalue like~/.ssh/id_ed25519.pubwould fail with a file-not-found error. Git itself expands~here, so this is a behaviour mismatch.Fix: expand the path with
Path.expanduser()before it is used as a file path.A regression test is included that configures
user.signingKeyas a tilde path and verifies signing succeeds.