Skip to content

[release/v1.65] Synchronize OWNERS_ALIASES file with Github teams#2011

Open
kubermatic-bot wants to merge 1 commit intorelease/v1.65from
update-release-v1.65-owners
Open

[release/v1.65] Synchronize OWNERS_ALIASES file with Github teams#2011
kubermatic-bot wants to merge 1 commit intorelease/v1.65from
update-release-v1.65-owners

Conversation

@kubermatic-bot
Copy link
Copy Markdown
Contributor

This pull request updates the OWNERS_ALIASES file based on the GitHub team associations.

/kind chore

Release Notes:

NONE

Documentation:

NONE

@kubermatic-bot kubermatic-bot added kind/chore Updating grunt tasks etc; no production code changes. release-note-none Denotes a PR that doesn't merit a release note. dco-signoff: yes Denotes that all commits in the pull request have the valid DCO signoff message. sig/cluster-management Denotes a PR or issue as being assigned to SIG Cluster Management. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Apr 14, 2026
@archups
Copy link
Copy Markdown
Contributor

archups commented Apr 17, 2026

/retest

@archups
Copy link
Copy Markdown
Contributor

archups commented Apr 17, 2026

/lgtm
/approve

@kubermatic-bot kubermatic-bot added the lgtm Indicates that a PR is ready to be merged. label Apr 17, 2026
@kubermatic-bot
Copy link
Copy Markdown
Contributor Author

LGTM label has been added.

DetailsGit tree hash: 63daaf8a73bf81367c150aec6b4903e9b679ecf3

@kubermatic-bot
Copy link
Copy Markdown
Contributor Author

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: archups
Once this PR has been reviewed and has the lgtm label, please assign mohamed-rafraf for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found 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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dco-signoff: yes Denotes that all commits in the pull request have the valid DCO signoff message. kind/chore Updating grunt tasks etc; no production code changes. lgtm Indicates that a PR is ready to be merged. release-note-none Denotes a PR that doesn't merit a release note. sig/cluster-management Denotes a PR or issue as being assigned to SIG Cluster Management. 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.

2 participants