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.
Expands revision parsing support:
adds
Repository.revparse_with_reference()
which maps togit_revparse_ext()
— takes the same arguments asrevparse_single()
but returns a 2-tuple(Object, Reference)
where the revspec is a reference eg:master
.a. ❓ Not sure on naming?
find_revision()
?b. ❓ Should we deprecate
Repository.revparse_single()
in favour of this rather than having two methods?c. ❓ Or merge them via something like
revparse_single(revspec, with_reference=True)
adds
Repository.revparse()
which maps togit_revparse()
— does range requests (eg:HEAD^1...new@{yesterday}
). Returns aRevSpec
object which has.from_object
,.to_object
, and.intents
properties.Adds a crude
repr()
implementation for Object-ish classes. eg:<pygit2.Object{commit:5ebeeebb320790caf276b9fc8b24546d63316533}>
. I kinda feel we should be adding usefulrepr()
methods to all classes going forward, otherwise debugging or exploration via a Python shell is unnecessarily slow.