-
Notifications
You must be signed in to change notification settings - Fork 277
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
Add release notes to the body of the pull request on create cherry-pick. #2884
Add release notes to the body of the pull request on create cherry-pick. #2884
Conversation
✅ Deploy Preview for kubernetes-sigs-kueue ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
/cc @tenzen-y |
/retest Due to #2885. |
/cc @alculquicondor |
TBH, I would like to work on the script improvement at k/k before we move this forward. |
I think it's a good idea! I will create PR on k/k. Thanks. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These changes are approved at kubernetes/kubernetes#126925.
@mbobrovskyi So, could you align only with approved changes?
Yes, that what we have. Only difference with Copyright year. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks.
/lgtm
/approve
LGTM label has been added. Git tree hash: cba1b9aadbac4e8d5f81caa06b47a995402cf627
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: mbobrovskyi, tenzen-y 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 |
What type of PR is this?
/kind bug
What this PR does / why we need it:
Add release notes to the body of the pull request on create cherry-pick.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?