semantic-release / semantic-release/github
`semantic-release` comments on already included PRs
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 534
- Forks
- 150
- Avg merge
- 1m
- Merged PRs (30d)
- 3
Description
We made our first release with semantic-release last week, and now we're pushing the next beta branch (1.1.0-beta.1). It seems that with the default configuration semantic-release comments on some PRs which were already included in the 1.0.0 release.
Is there a setting to comment only on the new PRs for each release, or at least PRs merged since the last production 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
Start by reproducing the default configuration with the 1.1.0-beta.1 branch and compare its comments with the PRs included in the 1.0.0 release. Review the release-commenting behavior and configuration options; done means comments are limited to new PRs or PRs merged since the last production release.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github, javascript
- Domain
- release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100