semantic-release / semantic-release/github
Recursively go through PRs when adding "included in release" message.
Open
Nobody has claimed this yet.
blocked
feature
plugin:github
- Dominant language
- JavaScript
- Stars
- 534
- Forks
- 150
- Avg merge
- 1m
- Merged PRs (30d)
- 3
Description
when working with feature branches, only the branch/PR itself gets a comment - it would be awesome if all PRs merged previously into feature branch also could get a comment. 🎉
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 tracing the existing logic that adds the “included in release” comment and how it identifies merged pull requests in feature branches. Done means recursively finding those earlier pull requests and adding the release message to each one; verify the behavior with the repository’s existing tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github, javascript
- Domain
- api, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100