merge_bases not wrapped
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.7k
- Forks
- 408
- Avg merge
- 2d 57m
- Merged PRs (30d)
- 7
Description
While the documentation for libgit2 has both merge_base and merge_bases the documentation for pygit2 only has the former.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Compare pygit2's documentation for merge_base with libgit2's documentation for merge_bases, then locate the corresponding pygit2 wrapper entry point. The work is done when merge_bases is exposed consistently and the documentation build confirms the missing API is covered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, python
- Domain
- backend-api-design, documentation
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100