Change log or release history?
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 325
- Forks
- 139
- PR merge metrics
- No merged PRs in 30d
Description
Is there any consolidated info on the changes between versions, a change log perhaps?
It would be really nice if the releases were tagged in github and had information about the changes since the last version. And/or there could be a CHANGELOG.md. It's difficult to upgrade if we have to read the diffs of every commit to see what changed!
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
Review the repository's GitHub releases and tags to identify the version history that should be consolidated. Use the proposed CHANGELOG.md as the documentation target; done means users can find the changes between versions without reading every commit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- documentation, release
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100