Update teams.yaml

[Nivedita-coder]

Updated the ci-signal as release-team-ci-signal

/cc @leonardpahlke @reylejano

[leonardpahlke]

Thanks @Nivedita-coder :)

/hold

I think some more references needs to be updated in other repos (ref @reylejano comment https://kubernetes.slack.com/archives/C2C40FMNF/p1664383282833649?thread_ts=1664382614.855319&channel=C2C40FMNF&message_ts=1664383282.833649)

[palnabarun]

do we have any other references to the team?

[leonardpahlke]

not that I know of

[leonardpahlke]

/unhold

[mrbobbytables]

is this still a thing? the PR is pretty old at this point

[leonardpahlke]

Yes. I think, we should merge this so that the sig-release/release-team teams are named consistently.

[leonardpahlke]

/lgtm

[leonardpahlke]

FYI 1.27 ci-signal lead @lauralorenz

[reylejano]

is this still a thing? the PR is pretty old at this point

@mrbobbytables I think this PR is still valid. This PR reflects a name change for ci-signal to add the release prefix so that it aligns with the other release related teams/subteams
https://github.com/kubernetes/org/blob/main/config/kubernetes/sig-release/teams.yaml#L301-L335

/cc @salaxander @JamesLaverack

[reylejano]

/lgtm

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Mark this PR as fresh with /remove-lifecycle stale
• Close this PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[mrbobbytables]

the name of the team can't be changed directly like this. It needs to add a previously

org/config/kubernetes/sig-architecture/teams.yaml

Lines 70 to 71 in f8b8c12

	previously:
	- features-maintainers

Also please make the commit message a bit more clear than 'update the name'.

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Mark this PR as fresh with /remove-lifecycle rotten
• Close this PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[nikhita]

@Nivedita-coder can you update the PR based on the changes requested?

[k8s-ci-robot]

New changes are detected. LGTM label has been removed.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• config/kubernetes/sig-release/OWNERS

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]

PR needs rebase.

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.

[k8s-ci-robot]

@Nivedita-coder: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-org-test-all	296414b	link	true	/test pull-org-test-all
pull-org-verify-all	296414b	link	true	/test pull-org-verify-all

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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. I understand the commands that are listed here.

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Reopen this PR with /reopen
• Mark this PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

[k8s-ci-robot]

@k8s-triage-robot: Closed this PR.

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Reopen this PR with /reopen
• Mark this PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

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.