-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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 the release-note-none to dependabot #4997
Conversation
Without the release label, dependabot PRs cannot be merged. Altering the PR to add the label means that dependabot won't be able to manage its PR anymore, so adding the release note label by default. Signed-off-by: Andrea Frittoli <[email protected]>
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dibyom 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 |
Setting the release note to |
/lgtm |
That would be in the PR description created by dependabot, or are you thinking of some other place we should document it? |
Thanks @afrittoli Yeah I was thinking of including it in the release notes. So the dependabot PRs has the details in the PR title that its upgrading a package from one version to the other. If we can automatically capture the same details in the PR release notes such that the release manager (task) can list them in a separate section when creating a release. |
Changes
Without the release label, dependabot PRs cannot be merged.
Altering the PR to add the label means that dependabot won't
be able to manage its PR anymore, so adding the release note
label by default.
Signed-off-by: Andrea Frittoli [email protected]
/kind misc
Submitter Checklist
As the author of this PR, please check off the items in this checklist:
functionality, content, code)
(if there are no user facing changes, use release note "NONE")
Release Notes