chore(ci): enable release-please-action on release branches#1032
Open
emersion wants to merge 2 commits into
Open
chore(ci): enable release-please-action on release branches#1032emersion wants to merge 2 commits into
emersion wants to merge 2 commits into
Conversation
aiAdrian
approved these changes
May 26, 2026
aiAdrian
left a comment
aiAdrian
left a comment
Contributor
There was a problem hiding this comment.
LGTM -> we might append the links in the PR comments to our docuementation. But this is commen behavior, might we don't need to "waste" words for own documentation.
louisgreiner
approved these changes
May 26, 2026
This lets maintainers create branches named e.g. "v2.11" and backport bugfixes to these branches via `git cherry-pick -x`. The GitHub action will then open a pull request to release a new bugfix version. See this README section about release branches: https://github.com/googleapis/release-please-action#supporting-multiple-release-branches See this GitHub docs section about glob patterns: https://docs.github.com/en/actions/reference/workflows-and-actions/workflow-syntax#filter-pattern-cheat-sheet Signed-off-by: Simon Ser <contact@emersion.fr>
Document how to use the workflow introduced in the previous commit. Signed-off-by: Simon Ser <contact@emersion.fr>
emersion
force-pushed
the
emr/release-please-release-branch
branch
from
b5dd429 to
6413a4d
Compare
Member
Author
|
@aiAdrian, I've added some docs explaining how to use release branches. Does this help? Anything missing? |
Member
Author
|
@aiAdrian, does this new version look good to you? |
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.
This lets maintainers create branches named e.g. "v2.11" and backport bugfixes to these branches via
git cherry-pick -x. The GitHub action will then open a pull request to release a new bugfix version.See this README section about release branches:
https://github.com/googleapis/release-please-action#supporting-multiple-release-branches
See this GitHub docs section about glob patterns:
https://docs.github.com/en/actions/reference/workflows-and-actions/workflow-syntax#filter-pattern-cheat-sheet