Consider providing a changelog and git tags
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 234
- Forks
- 108
- Avg merge
- 5h 12m
- Merged PRs (30d)
- 4
Description
Hi! Thank you for this crate.
I have this crate in my dependency tree and was just about to upgrade it from 0.23 to 0.24. When upgrading dependencies I always check what has changed, in case there is something important I should know about. But either I'm unable to find this information or it's not available for this crate. There are no git tags marking which commit is actually the releases on crates.io, nor any changelog file outlining the changes. Could you consider adding these things? I believe it improves the overall quality of a crate quite significantly.
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
No files or tests are named. Inspect the repository's release history and the versions published on crates.io first; done means a changelog outlines the changes and git tags identify the commits corresponding to releases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, rust
- Domain
- documentation, release
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- Half a day
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100