Skip to content

🌱 chore: title verifier update#5300

Merged
k8s-ci-robot merged 1 commit intokubernetes-sigs:mainfrom
richardcase:verify_update
Jan 21, 2025
Merged

🌱 chore: title verifier update#5300
k8s-ci-robot merged 1 commit intokubernetes-sigs:mainfrom
richardcase:verify_update

Conversation

@richardcase
Copy link
Copy Markdown
Member

What type of PR is this?

/kind cleanup

What this PR does / why we need it:

Updates the PR title checker to be inline with upstream CAPI. Also, this will help with some PR failures with auth.

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

Special notes for your reviewer:

Checklist:

  • squashed commits
  • includes documentation
  • includes emojis
  • adds unit tests
  • adds or updates e2e tests

Release note:

Update PR verifier to be inline with upstream CAPI.

Updates the PR title checker to be inline with upstream CAPI. Also,
this will help with some PR failures with auth.

Signed-off-by: Richard Case <richard.case@outlook.com>
@k8s-ci-robot k8s-ci-robot added release-note Denotes a PR that will be considered when it comes time to generate release notes. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. labels Jan 21, 2025
@k8s-ci-robot k8s-ci-robot added needs-priority size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Jan 21, 2025
@richardcase
Copy link
Copy Markdown
Member Author

/cherrypick release-2.7
/cherrypick release-2.6
/cherrypick release-2.5
/cherrypick release-2.4

@k8s-infra-cherrypick-robot
Copy link
Copy Markdown

@richardcase: once the present PR merges, I will cherry-pick it on top of release-2.4, release-2.5, release-2.6, release-2.7 in new PRs and assign them to you.

Details

In response to this:

/cherrypick release-2.7
/cherrypick release-2.6
/cherrypick release-2.5
/cherrypick release-2.4

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-sigs/prow repository.

@nrb
Copy link
Copy Markdown
Contributor

nrb commented Jan 21, 2025

/approve
/hold
/assign @damdo @AndiDog

Feel free to remove hold if it gets the lgtm.

@k8s-ci-robot k8s-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jan 21, 2025
@k8s-ci-robot
Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: nrb

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 21, 2025
@nrb
Copy link
Copy Markdown
Contributor

nrb commented Jan 21, 2025

/lgtm
/unhold

@k8s-ci-robot k8s-ci-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jan 21, 2025
@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jan 21, 2025
@k8s-ci-robot k8s-ci-robot merged commit 1c280ad into kubernetes-sigs:main Jan 21, 2025
@k8s-infra-cherrypick-robot
Copy link
Copy Markdown

@richardcase: new pull request created: #5302

Details

In response to this:

/cherrypick release-2.7
/cherrypick release-2.6
/cherrypick release-2.5
/cherrypick release-2.4

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-sigs/prow repository.

@k8s-infra-cherrypick-robot
Copy link
Copy Markdown

@richardcase: new pull request created: #5303

Details

In response to this:

/cherrypick release-2.7
/cherrypick release-2.6
/cherrypick release-2.5
/cherrypick release-2.4

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-sigs/prow repository.

@k8s-infra-cherrypick-robot
Copy link
Copy Markdown

@richardcase: new pull request created: #5307

Details

In response to this:

/cherrypick release-2.7
/cherrypick release-2.6
/cherrypick release-2.5
/cherrypick release-2.4

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-sigs/prow repository.

@k8s-infra-cherrypick-robot
Copy link
Copy Markdown

@richardcase: new pull request created: #5308

Details

In response to this:

/cherrypick release-2.7
/cherrypick release-2.6
/cherrypick release-2.5
/cherrypick release-2.4

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-sigs/prow repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. lgtm "Looks good to me", indicates that a PR is ready to be merged. needs-priority release-note Denotes a PR that will be considered when it comes time to generate release notes. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants