di-sukharev / di-sukharev/opencommit
[Feature]: Add Changelog of version
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 7.5k
- Forks
- 445
- Avg merge
- 18m
- Merged PRs (30d)
- 2
Description
Description
I think it's important to know what changes are involved on each new version of the tool
Suggested Solution
Use the tag/releases of github to add a short description that matches the version published on npmjs
Alternatives
No response
Additional Context
No response
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
Start by reviewing the repository's GitHub tags and releases alongside the versions published on npmjs. Done means each published version has a short changelog description that matches the corresponding release. The issue does not name a file or existing release workflow, so inspect how releases are currently managed before starting.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- documentation, release
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100