libgit2 / libgit2/libgit2sharp
`PatchEntryChanges` test coverage
Open
Nobody has claimed this yet.
Easy fix
Up for grabs
- Dominant language
- C#
- Stars
- 3.5k
- Forks
- 925
- PR merge metrics
- No merged PRs in 30d
Description
#702 introduced new properties on PatchEntryChanges. It would be good to have unit tests covering them.
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
Locate the PatchEntryChanges type and read issue #702 to identify the new properties. Inspect nearby unit-test conventions, add coverage for those properties, and run the relevant test project to confirm the tests pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, git
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100