libgit2 / libgit2/libgit2sharp
Perform Final Review of the API before v1.0 Locks It
Open
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 3.5k
- Forks
- 925
- PR merge metrics
- No merged PRs in 30d
Description
All owners, collaborators, and interested parties should do a sweep of the API now, before v1.0 is reached and adjustments to the API become very burdensome to perform.
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
The issue names no files, tests, or entry points. Start by surveying the public API and its owners and collaborators, then document any needed adjustments before v1.0; completion would mean the API sweep is finished and the required changes are recorded.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100