forked from libgit2/libgit2sharp
-
Notifications
You must be signed in to change notification settings - Fork 0
Update PR #1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
Jer512
wants to merge
724
commits into
Jer512:master
Choose a base branch
from
libgit2:master
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Update PR #1
Conversation
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
Include the error code as a first-class citizen of exceptions that correspond to libgit2 errors. Previously, we would store the error code in exception data when creating the exception from a libgit2 native error. However, we may also want to _generate_ these exceptions and have them converted to a libgit2 error. (For example, a callback may want to return GIT_EUSER, and so throw a `UserCancelledException`.) Therefore, provide exceptions with knowledge of their corresponding libgit2 error code so that we can round-trip that data.
Provide certificate callback functionality when using the managed HTTP smart subtransport.
Continue to allow a custom subtransport to override our own.
Throwing an exception in a native callback is pointless; instead, carefully protect the entry points to return a native error code (-1) on failure. Wrap everything else in a try/catch to propagate error codes.
We (may) explicitly remove HTTPS from libgit2.
Use the .NET standard HTTP class for the Managed HTTP subtransport
The passthrough error code for SSL validation means that the caller declined to act; we should just use our default validation in this case.
This resolves the warning we see on Azure Pipelines about the soon-to-be-removed image.
Update macOS image on Azure Pipelines
Co-Authored-By: dallmair <[email protected]>
Suppress Expect: 100 Continue header
HttpClient disposes it for you with the handler we're calling.
* Remove unneeded cast * Use SafeHandles
* Added Depth as a fetch option * Map Depth from FetchOptions to GitFetchOptions * Added tests for shallow cloning
Update LibGit2Sharp.NativeBinaries to 2.0.323
Add a CloneOptions constructor that takes a FetchOptions
…_creates_an_empty_folder_for_the_worktree Fix empty folder issue in Repositoy.Worktrees.Add
Make owner validation configurable
…te-stream fix #2071 ObjectDatabase.Write<T>(Stream, long) does not respect T
Test and fix for #1869
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.