Repository navigation
feat: flag PRs that only join an already-pending release - #23
Merged
Merged
Conversation
Contributor
🤖 release-please PREVIEWWhat merging this PR into 🤖 I will create a release beep boop1.6.0 (2026-10-07)Features
This PR was generated with Release Please. See documentation. Two entries, one change: release-please reads both the commit on this branch and the merge commit GitHub will create, whose body is this PR title. Both really do land in the published changelog. Only the merge commit has no SHA to cite, because it does not exist yet. Predicted from |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #22. For a PR that adds nothing releasable while a release is already pending on the base, the preview now says so up front (
A release is already pending on master (vX, a Y bump), and this PR is not what causes it), keeps the pending changelog in a collapsed section, applies a separateRELEASE PENDINGlabel (inputpending-label) instead ofRELEASE, and sets a newpr-contributesoutput tofalse. It works by dry-running release-please on the base branch too and comparing changelogs.Tested under
actagainst a scratch repo with a pending feat on master: chore PR gives the banner and fold, feat PR givespr-contributes=true. Label handling is untested (needs a real PR).