di-sukharev / di-sukharev/opencommit
[Feature]: Generate release notes
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 7.5k
- Forks
- 445
- Avg merge
- 18m
- Merged PRs (30d)
- 2
Description
Description
Given a repo where releases are tagged, provide a way to generate a set of release notes based on the difference between the current state of the repo and the state it was at the last tagged release.
Suggested Solution
Ideally something as simple as oco --changedsince <tag> or similar from a user experience point of view. The output should just go to stdout so it can be redirected as appropriate.
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
The issue names no files or tests; start by locating the CLI entry point and existing Git command handling. Trace how a tag can be compared with the current repository, then verify that the feature accepts a tag and writes the resulting release notes to stdout for redirection.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, javascript
- Domain
- cli, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100