Standard merge - #589
Merged
jdgarcia merged 2 commits intoMay 22, 2015
Merged
Standard merge#589jdgarcia merged 2 commits into
jdgarcia merged 2 commits into
Conversation
Copy link
Copy Markdown
Collaborator
Sorry, something went wrong.
Copy link
Copy Markdown
Collaborator
Author
|
"hey, tests passed" |
Sorry, something went wrong.
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.
Enabled git_merge (NodeGit.Merge() and NodeGit.Merge.merge) and added a convenience method.
git_merge is the standard merge that merges into HEAD and writes the MERGE_* to the git repo which is the indicator that the repo is currently in a merge state. (git_repository_state looks for those files to determine if it's in a merge state)
Other merge methods, such as Merge.commits don't actually leave the repo in a merge state