-
Notifications
You must be signed in to change notification settings - Fork 533
Support merge-base #370
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
Support merge-base #370
Conversation
5fb2459
to
008bdce
Compare
cc30bd4
to
153ab76
Compare
Bump. Is there something I can help with to move this along? |
@EPecherkin Can you please add DCO to your commits? Thank you. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. 👍
@EPecherkin Please add the DCO and we'll merge this ASAP. |
Signed-off-by: Evgenii Pecherkin <evgenii@toptal.com>
418de57
to
cf8aa6d
Compare
Hi, Is it possible to add "--is-ancestor" parameter as well? |
Signed-off-by: Evgenii Pecherkin <evgenii@toptal.com> Signed-off-by: invist@thinkpwn <cf@cw>
@ngergo100
Please add this as a separate PR/GitHub issue. I will close this now and we can continue the discussion there. |
Add support for
git merge-base
, which finds as good common ancestors as possible for a mergeUsage example:
g.merge_base('branch1', 'branch2', ..., options)
Possible options:
The method returns an array of
Git::Object::Commit
. The amount of items depends on the particular case