git_trace_set in Rugged
Open
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 2.3k
- Forks
- 293
- PR merge metrics
- No merged PRs in 30d
Description
It doesn't look like git_trace_set is implemented for Rugged. Is that true?
If not how does one activate tracing when using Rugged?
Contributor guide
No contributing guide indexed for this repository
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
Start by inspecting Rugged's bindings and the libgit2 entry point named git_trace_set; determine whether the API is exposed and how tracing is configured in the current versions. Done means the issue has a verified implementation status and, if supported, a documented activation path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, ruby
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100