semantic-release / semantic-release/release-notes-generator
release notes erroneously claim commit closes issue
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 368
- Forks
- 55
- Avg merge
- 10m
- Merged PRs (30d)
- 1
Description
This commit resulted in release notes that stated that the release closed the linked issue, when really it was just intended as reference. Have we considered doing keyword-matching on the preceding word like GitHub does in issue text?
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 comparing commit c10a29448de701fece6efeac3d82d577d1683701 with the v3.6.0 release notes to reproduce the incorrect issue closure. Then inspect the release-note generation and keyword handling described by the issue. Done means references without an issue-closing keyword no longer claim to close the linked issue, with matching behavior aligned with GitHub's rules.
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
- Mostly clear
- Newbie friendliness
- 35/100