tursodatabase / tursodatabase/libsql-client-ts
Changelog + contributing guidelines
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 576
- Forks
- 69
- PR merge metrics
- No merged PRs in 30d
Description
The latest release did not include an update to the CHANGELOG.
This might be easily fix with a tool like semantic-release.
On the other hand, this will need a contributing guideline regarding commits format and squashing them, for example try to compare version 0.6.0 and 0.6.1 to understand the issue.
Contributor guide
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
Compare releases v0.6.0 and v0.6.1 to identify what the CHANGELOG missed, then review the semantic-release proposal and the repository's current contribution process. Done means the release history is updated and contributing guidance clearly covers commit formatting and squashing, with any chosen release automation documented.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, release
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100