Skip to content

Fix the MULTIPLE_AREAS and multiple colon(:) in same line of the generated release notes. #12280

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.

Sign up for GitHub

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

Jump to bottom
Open
Tracked by #12123
chandankumar4 opened this issue May 23, 2025 · 2 comments
Open
Tracked by #12123

Fix the MULTIPLE_AREAS and multiple colon(:) in same line of the generated release notes. #12280

chandankumar4 opened this issue May 23, 2025 · 2 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. needs-priority Indicates an issue lacks a `priority/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@chandankumar4
Copy link
Contributor

What would you like to be added (User Story)?

Automate the process to fix MULTIPLE_AREAS and multiple colon(:) in the same line of generated release notes!!

Detailed Description

What's need to happen

  • Look for any MULTIPLE_AREAS entries. If the PR does indeed guarantee multiple areas, just remove the MULTIPLE_AREAS prefix and just leave the areas.
  • Remove the multiple colon(:) from a line.

Anything else you would like to add?

No response

Label(s) to be applied

/kind feature
One or more /area label. See https://github.com/kubernetes-sigs/cluster-api/labels?q=area for the list of labels.
@k8s-ci-robot k8s-ci-robot added kind/feature Categorizes issue or PR as related to a new feature. needs-priority Indicates an issue lacks a `priority/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels May 23, 2025
@k8s-ci-robot
Copy link
Contributor

This issue is currently awaiting triage.

If CAPI contributors determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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.

@sbueringer
Copy link
Member

sbueringer commented May 23, 2025 •
edited
Loading

Yeah I would just make multiple areas a regular case. In basically all cases this is intended and not an error. So we should just list the areas

@cprivitere cprivitere mentioned this issue May 23, 2025
Open
42 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/feature Categorizes issue or PR as related to a new feature. needs-priority Indicates an issue lacks a `priority/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
CAPI v1.11 release improvement tasks
Status: No status
Milestone
No milestone
Development

No branches or pull requests
3 participants
@sbueringer @k8s-ci-robot @chandankumar4