Create a GitHub action to check PR title

[varodrig]

Create a GitHub action that will check the PR title to make sure it aligns with the rules

The rules are:

component_name: description

For example:
pipelines: Fixed broken link in Getting Started with Kubeflow Pipelines
website: Fixed style issues on main page

List of components/areas:

Requested by @andreyvelich in regards of PR #3965

[andreyvelich]

/good-first-issue

[google-oss-prow]

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

Please ensure the request meets the requirements listed here.

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.

[thesuperzapper]

People might be able to use the one we created for kubeflow/notebooks:

• https://github.com/kubeflow/notebooks/blob/main/.github/workflows/semantic-prs.yaml

But I am not sure what the valid list of {semantic_prefix}: should be, because there are PRs which affect content, and there are PRs that affect the website itself, like #3981

[pboyd]

I'd be happy to take a crack at this. The semantic PR action looks like it could be coerced into doing what's needed, but this action looks like it was intended to do exactly what's requested here.

Is this a sufficient list for the allowed component names?

• central-dash
• katib
• model-registry
• notebooks
• pipelines
• spark-operator
• trainer
• website

These are the directory names under content/en/docs/components with a catch-all (website) for anything that doesn't fit. Thoughts?

[varodrig]

I'd be happy to take a crack at this. The semantic PR action looks like it could be coerced into doing what's needed, but this action looks like it was intended to do exactly what's requested here.

Is this a sufficient list for the allowed component names?

• central-dash
• katib
• model-registry
• notebooks
• pipelines
• spark-operator
• trainer
• website

These are the directory names under content/en/docs/components with a catch-all (website) for anything that doesn't fit. Thoughts?

Thanks @pboyd for looking into this. You can see the full list of components's name here
https://raw.githubusercontent.com/kubeflow/website/refs/heads/master/.github/ISSUE_TEMPLATE/BUG_REPORT.md

[vikas-saxena02]

@varodrig I have done a PR #4018 for this. Please review.

[pboyd]

I didn't see #4018 in time. I'll close #4020..

[varodrig]

/assign @vikas-saxena02