libgit2 / libgit2/rugged

Outdated CHANGELOG

Open
#641 1 comment 9 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
2.3k
Forks
293
PR merge metrics
No merged PRs in 30d

Description

The CHANGELOG hasn't been updated since July 2015, over a year ago. There have been stable releases since then. An outdated CHANGELOG makes it more difficult for users to decide if a version bump is needed as they no longer have a quick overview of what's been changed.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the CHANGELOG and review the stable releases published since July 2015. Done means the file provides a current overview of changes for those releases so users can judge whether a version bump is needed.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.