Link to docs
Open
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 2.3k
- Forks
- 293
- PR merge metrics
- No merged PRs in 30d
Description
While README.md mostly covers popular use cases, I found that https://www.rubydoc.info/github/libgit2/rugged/Rugged/Branch is still an invaluable reference, which is not linked from the main page. Definitely useful.
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
Open README.md and review how the main page links to existing references. Add a link to the Rugged::Branch documentation at https://www.rubydoc.info/github/libgit2/rugged/Rugged/Branch; the work is done when readers can reach this reference from the README.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100