community
community copied to clipboard
kubernetes
changed the marketing-team subdirectory name to contributor-comms
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: harshitasao
Once this PR has been reviewed and has the lgtm label, please assign cblecker for approval by writing /assign @cblecker in a comment. For more information see:The Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.
- committee-steering/OWNERS
- communication/OWNERS
- elections/steering/2020/OWNERS
- events/OWNERS
- mentoring/OWNERS
- sig-contributor-experience/OWNERS
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
@harshitasao: The following test 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-community-verify | 8095406906f56b0dfce506a492fd6a31599a392e | link | true | /test pull-community-verify |
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.
Thank you @MadhavJivrajani and @chris-short I'll make the following changes.
@MadhavJivrajani I've created a separate PR for the changes to sigs.yaml, as Chris suggested in the comment. So, should I close that and add the changes here or run the make generate command there?
@harshitasao I think probably just run the make generate command there. Also where is that PR, so we can help with it?
Please feel free to reach out to us /sig auth for additional reviews.
/remove-sig auth
@harshitasao: 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.
@harshitasao in case you need it: https://timonweb.com/misc/how-to-update-a-forked-repo-from-an-upstream-with-git-rebase-or-merge/
@kaslin and I have to do this fairly often so please don't hesitate to reach out via Slack.
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue or PR as fresh with
/remove-lifecycle stale - Mark this issue or PR as rotten with
/lifecycle rotten - Close this issue or PR with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: harshitasao
Once this PR has been reviewed and has the lgtm label, please assign cblecker for approval by writing /assign @cblecker in a comment. For more information see the Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.
- committee-steering/OWNERS
- communication/OWNERS
- elections/steering/2020/OWNERS
- events/OWNERS
- mentoring/OWNERS
- sig-contributor-experience/OWNERS
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
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/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas 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
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/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas 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-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/staleis applied- After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied- After 30d of inactivity since
lifecycle/rottenwas applied, the PR is closedYou 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.