Updated input docs to allow for git_push_update_reference_cb to generate #1386
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
cjhoward92
changed the title
Member
|
@cjhoward92 rebase please! |
cjhoward92
force-pushed
the
add_push_updated_reference
branch
from
3146350 to
d385fbf
Compare
Member
|
Is this still wip? |
Collaborator
Author
|
I am verifying that it builds |
cjhoward92
changed the title
Collaborator
Author
|
Good to go. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Requires libgit2 be bumped to the current master branch before this can be merged. These changes allow for the
git_push_update_reference_cbto be generated in NodeGit, allowing for clients to determine if a remote ref rejected an update however still returned a valid response. An example would be when you push to a protected branch on GitHub.