Skip to content
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

Implement is_ancestor #322

Merged
merged 1 commit into from
Jul 21, 2015
Merged

Conversation

bwrsandman
Copy link

Wrap git merge-base --is-ancestor into its own function because it acts
as a boolean check unlike base git merge-base call

@Byron Byron added this to the v1.0.2 - Fixes milestone Jul 21, 2015
@Byron
Copy link
Member

Byron commented Jul 21, 2015

Thank you !

Have you managed to get nosetest to work for you ? It should be easy to add a test to verify that

  • it returns True the rev is an ancestor
  • it returns False if the rev is no ancestor
  • it throws if there is an invalid revision

@bwrsandman
Copy link
Author

I am writing a test as we speak

@bwrsandman bwrsandman force-pushed the is_ancestor branch 2 times, most recently from d402f7b to acc559f Compare July 21, 2015 14:58
Wrap `git merge-base --is-ancestor` into its own function because it acts
as a boolean check unlike base `git merge-base call`
@bwrsandman
Copy link
Author

Test done. Sorry I have no video of the coding ;)

@Byron
Copy link
Member

Byron commented Jul 21, 2015

Thank you !

Looks great, even without the video :).

Closes #321

Byron added a commit that referenced this pull request Jul 21, 2015
@Byron Byron merged commit 1883eb9 into gitpython-developers:master Jul 21, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants