📖 Add call out for area labels when making a PR

[joekr]

What this PR does / why we need it:
We would like users to add labels to their PRs. This will help the release team know the areas of the code base update for better release notes.

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

What type of PR is this?

/area documentation

[k8s-ci-robot]

@joekr: The label(s) area/documentation cannot be applied, because the repository doesn't have them.

In response to this:

What this PR does / why we need it:
We would like users to add labels to their PRs. This will help the release team know the areas of the code base update for better release notes.

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

What type of PR is this?

/area documentation

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.

[joekr]

I'm not sure who to work with regarding adding labels, but we probably want to have:

• documentation (or docs)
• ClusterClass
• KCP
• we have testing but what about e2e-testing or test/e2e
• CI
• Server-Side-Apply (or SSA)

@oscr might have more label suggestions as well.

[killianmuldoon]

/lgtm

It's relatively easy to add and remove area labels, so it's fine to take an iterative approach there. I think, if this is the agreed upon approach, we could also add a /needs-area label to all PRs that don't have one, which gives a hint to reviewers to add the label.

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 5974f77948fc02f0c4db709619f817dd82496f4c

[killianmuldoon]

@joekr Could you open an issue to discuss cleaning up the existing area labels and adding new useful ones?

/retitle 📖 Add call out for area labels when making a PR

[sbueringer]

+1 to figure out which area labels we want via an issue. I can give some input there

[fabriziopandini]

should this go down into What type of PR is this?

[nprokopic]

+1 here, number 2 above sounds like it should go into "What type of PR is this?"

[chrischdi]

Suggested change

	Area example:
	Example for adding an area label (see https://github.com/kubernetes-sigs/cluster-api/labels?q=area for the list of available labels):

[joekr]

thanks for the call out. I forgot about this PR 😵‍💫

[joekr]

Line 14 has this called out instead.

[chrischdi]

/lgtm

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: c2dad8a7a0dfa20f0539a05d2c71aa884e990cb7

[furkatgofurov7]

Suggested change

	Please label this pull request according to what area(s) you are addressing. For reference on on PR/issue labels: https://github.com/kubernetes-sigs/cluster-api/labels?q=area+
	Please label this pull request according to what area(s) you are addressing. For reference on PR/issue labels, see: https://github.com/kubernetes-sigs/cluster-api/labels?q=area+

[nprokopic]

/lgtm

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: bb853c928c2fc89f9a7df95274699c00e92a0dd5

[killianmuldoon]

/lgtm
/approve

/hold

for @sbueringer

[sbueringer]

/lgtm
/approve

/hold cancel

Thx!

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: killianmuldoon, sbueringer

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:

• OWNERS [killianmuldoon,sbueringer]

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