Enforce some standards for PR titles

[ditsuke]

/kind feature

Describe the solution you'd like CAPI uses the kubernetes-sigs/kubebuilder-release-tools action to enforce some standards in PR titles. These standards require emoji prefixes to PR titles, which make release note generation and visually scanning through PRs convenient.

Anything else you would like to add: This should be a really straightforward addition (a single workflow), happy to take this up myself or have a new contributor work on it once the issue is validated.

[ditsuke]

/good-first-issue

[k8s-ci-robot]

@ditsuke: This request has been marked as suitable for new contributors.

Guidelines

Please ensure that the issue body includes answers to the following questions:

• Why are we solving this issue?
• To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
• Does this issue have zero to low barrier of entry?
• How can the assignee reach out to you for help?

For more details on the requirements of such an issue, please see here and ensure that they are met.

If this request no longer meets these requirements, the label can be removed by commenting with the /remove-good-first-issue command.

In response to this:

/good-first-issue

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.

[AectannArd]

Hi @ditsuke Could you please assign the issues to me please. It should be quite straightforward to handle

[ditsuke]

/assign @AectannArd

[AectannArd]

@ditsuke unfortunately review has hung for a while

can I do anything to speed it up?

[ditsuke]

@AectannArd unfortunately not, I'll give it a look for you but we'll need a maintainer for approval.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale