-
Notifications
You must be signed in to change notification settings - Fork 1.1k
[1.18] Allow release notes for release branches #3766
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[1.18] Allow release notes for release branches #3766
Conversation
This changes the release notes generation script to also work for release branches. Signed-off-by: Sascha Grunert <[email protected]>
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: saschagrunert The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: saschagrunert The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
LGTM |
|
/lgtm |
|
/cherry-pick master |
|
@haircommander: #3766 failed to apply on top of branch "master": In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
1 similar comment
|
@haircommander: #3766 failed to apply on top of branch "master": In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
Hm, I'll cherry-pick manually |
What type of PR is this?
/kind feature
What this PR does / why we need it:
This changes the release notes generation script to also work for
release branches.
Which issue(s) this PR fixes:
None
Special notes for your reviewer:
Needs a forward-port to the master branch as well.
Does this PR introduce a user-facing change?