jackTabsCode / jackTabsCode/asphalt
Changelog file
Open
Nobody has claimed this yet.
documentation
- Dominant language
- Rust
- Stars
- 160
- Forks
- 37
- PR merge metrics
- No merged PRs in 30d
Description
We should maintain a changelog file. We'll have to include a section for all previous releases (the patch notes of which can be found on the Releases page), and also maintain an unreleased section.
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 reviewing the repository's Releases page and collect the patch notes for each previous release. Create the changelog file with a section for every previous release and an Unreleased section; it is done when all listed releases are represented and the file can be updated for future changes.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100