semantic-release / semantic-release/release-notes-generator
Diffhunks read as related issues and associated PRs
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 368
- Forks
- 55
- Avg merge
- 10m
- Merged PRs (30d)
- 1
Description
When a commit body includes a diffhunk://# as in the case of https://github.com/babblebey/starlight-page-context-action/pull/7 for example with a diffhunk used in the PR description. Issue parser read this link as though is is an associated PR or a related issue hence leading to production of a release note with the diffhunk as issue/pr a commit closes
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
Reproduce the parser behavior using the diffhunk://# link in the referenced pull request and compare it with the generated release for version 0.4.1. Trace the issue and pull-request reference parsing entry point, then verify that diffhunk links are excluded while genuine associated issues and PRs remain included.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- release
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100