feat: support for skip-labeling parameter for GitHub action#1066
Merged
chingor13 merged 10 commits intogoogleapis:mainfrom Mar 7, 2025
Merged
feat: support for skip-labeling parameter for GitHub action#1066chingor13 merged 10 commits intogoogleapis:mainfrom
chingor13 merged 10 commits intogoogleapis:mainfrom
Conversation
Contributor
Author
|
@chingor13 Could you take a look at this, please. |
chingor13
approved these changes
Mar 7, 2025
Contributor
chingor13
left a comment
There was a problem hiding this comment.
This seems like an option that does belong here vs. in the manifest config
github-merge-queue Bot
pushed a commit
that referenced
this pull request
Mar 7, 2025
🤖 I have created a release *beep* *boop* --- ## [4.2.0](v4.1.5...v4.2.0) (2025-03-07) ### Features * support for skip-labeling parameter for GitHub action ([#1066](#1066)) ([fb7f385](fb7f385)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
|
@huksley when would you use skip labeling? In this case the action would always create a new pr and never create any release. Am I wrong? |
Contributor
Author
|
@kalosisz Hi, we don't do package releases. we run release-please to create changelog and prepare a release version of our platform, which is deployed when you merge the pull request from release-please. That way we promote staging (main branch) to a production release. Perhaps, we don't need the autolabel "autorelease:pending", but perhaps something different? |
software-dev-web
added a commit
to software-dev-web/please-action
that referenced
this pull request
Dec 11, 2025
🤖 I have created a release *beep* *boop* --- ## [4.2.0](googleapis/release-please-action@v4.1.5...v4.2.0) (2025-03-07) ### Features * support for skip-labeling parameter for GitHub action ([#1066](googleapis/release-please-action#1066)) ([fb7f385](googleapis/release-please-action@fb7f385)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
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
3 participants
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.
Adds support and documentation for the skipLabeling option when running release-please from GitHub Actions.
This option in the config are ignored when running in release-please-action, and only honored when you pass it as an option via a command line. This PR adds the same support to GitHub action.