Skip to content

Conversation

@utam0k
Copy link
Member

@utam0k utam0k commented Aug 1, 2025

What type of PR is this?

/kind documentation

What this PR does / why we need it:

Hi everyone, I would like to self-nominate to become a SIG Scheduling reviewer:

Also, I contributed the sub project in sig-scheduling:

I created a PR based on the previous one #129781, but please let me know if there is anything else I need.

Which issue(s) this PR is related to:

Special notes for your reviewer:

Thank you all!

Does this PR introduce a user-facing change?

None

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:


@k8s-ci-robot k8s-ci-robot added release-note-none Denotes a PR that doesn't merit a release note. kind/documentation Categorizes issue or PR as related to documentation. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. do-not-merge/needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Aug 1, 2025
@k8s-ci-robot
Copy link
Contributor

This issue is currently awaiting triage.

If a SIG or subproject determines 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.

Details

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-ci-robot k8s-ci-robot added the needs-priority Indicates a PR lacks a `priority/foo` label and requires one. label Aug 1, 2025
@utam0k
Copy link
Member Author

utam0k commented Aug 1, 2025

/retest-required

@utam0k utam0k force-pushed the add-utam0k-sig-scheduling-reviwer branch from 7e05d10 to b080dba Compare August 1, 2025 13:06
@sanposhiho
Copy link
Member

+1
He has helped a lot, especially recently. Thanks for the contribution, and looking forward to keeping this collaboration!

@macsko
Copy link
Member

macsko commented Aug 4, 2025

+1
Thanks for your help and contributions!

@macsko
Copy link
Member

macsko commented Aug 4, 2025

/sig scheduling

@k8s-ci-robot k8s-ci-robot added sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling. and removed do-not-merge/needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Aug 4, 2025
@utam0k
Copy link
Member Author

utam0k commented Aug 4, 2025

/assign dims

@aojea
Copy link
Member

aojea commented Aug 4, 2025

not directly involved in the SIG but I also want to give my +1 for a well deserved promotion in the contributor ladder

@dims
Copy link
Member

dims commented Aug 6, 2025

/approve
/lgtm

(will be able to land only after code freeze is lifted)

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Aug 6, 2025
@k8s-ci-robot
Copy link
Contributor

LGTM label has been added.

DetailsGit tree hash: 392e1201f6423b8c264fbc92b5e7e74deeb20279

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dims, utam0k

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 Aug 6, 2025
@k8s-ci-robot k8s-ci-robot merged commit 1b0bf0a into kubernetes:master Aug 28, 2025
13 checks passed
@k8s-ci-robot k8s-ci-robot added this to the v1.35 milestone Aug 28, 2025
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/documentation Categorizes issue or PR as related to documentation. lgtm "Looks good to me", indicates that a PR is ready to be merged. needs-priority Indicates a PR lacks a `priority/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. release-note-none Denotes a PR that doesn't merit a release note. sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants