semantic-release / semantic-release/github
Duplicated information in release notes.
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 534
- Forks
- 150
- Avg merge
- 1m
- Merged PRs (30d)
- 3
Description
When semantic release creates a GitHub release, it adds the version number and date to the release notes. This seems very unnecessary as it is essentially a duplicate of what already is shown by GitHub. Is there a reason why this information is added to every release?
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
The issue names no source file, test, or entry point. Start by locating where this plugin assembles GitHub release notes, then verify how the version and date are added; done means the duplication is removed or the intended behavior is clearly documented and covered by an appropriate test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, javascript
- Domain
- release
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100