contributor-playground icon indicating copy to clipboard operation
contributor-playground copied to clipboard

Published 20 hours ago • verified publisher icon kubernetes-sigs

check for cla

Open Aaina26 opened this issue 1 year ago • 3 comments

checking for cla

Aaina26 avatar Sep 26 '24 07:09 Aaina26

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: Aaina26 Once this PR has been reviewed and has the lgtm label, please assign rinkiyakedad 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:

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 avatar Sep 26 '24 07:09 k8s-ci-robot

CLA Signed

The committers listed above are authorized under a signed CLA.

  • :white_check_mark: login: Aaina26 / name: Aaina Lohia (409d77c8ae3d7070863a8030daeb17f268e7c0c5)

linux-foundation-easycla[bot] avatar Sep 26 '24 07:09 linux-foundation-easycla[bot]

Since this space is FOR PR SUBMISSION PRACTICE, NOT FOR SIGNING CLA, it would be best to write a PR title that is appropriate FOR PRACTICE TO PR CREATION like add <your github account>.md to remote/learners folder.

Also, I recommend that you do this in the /remote/learners/ directory, if so I can review it.

shu-mutou avatar Oct 16 '24 10:10 shu-mutou

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

k8s-triage-robot avatar Jan 14 '25 11:01 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

k8s-triage-robot avatar Feb 13 '25 12:02 k8s-triage-robot