You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@extrawurstssh-key is still a release candidate at 0.7.0-rc.10. I’m fine with merging as-is, but I wanted to at least have mentioned it. With respect to changes related to gitoxide, there’s nothing left on my to-do list.
Since #2464 got merged which removed the dependency on ssh-key, there’s no need any longer to wait for its new release, so this PR is now finally ready for review!
Yes! This enables sha256 for gix. I’ll soon open a follow-up PR that enables unstable-sha256 for git2 at which point we should have support for SHA-256 repositories in gitui. Based on what I know, most, if not all, APIs we use should already work with SHA-256 without us having to change anything.
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
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.
This is a follow-up to #2962.