search

kubernetes / community

Kubernetes community content
Apache License 2.0
11.92k stars 5.16k forks source link

stale bot feedback message is not helpful #6232

Closed grosser closed 2 years ago

grosser commented 2 years ago 
Please send feedback to sig-contributor-experience at kubernetes/community.

... link to an issue template or say what to put in title/body

/sig contributor-experience

AvineshTripathi commented 2 years ago

Hey @grosser I am not sure won't this issue come under sig/testing as they are responsible for the bot and stuff. Correct me if I missed anything

mrbobbytables commented 2 years ago

contribex is the right one for this 👍 We have lifecycle commands to flag issues, /lifecycle frozen is used for long term issues. For PRs, we have a lot of issues with them being abandoned and they SHOULD age out.

AvineshTripathi commented 2 years ago

Hey @mrbobbytables thank you for clarifying it :-)

grosser commented 2 years ago

"we have a lot of issues with them being abandoned and they SHOULD age out." they should only be age out if the requester abandons them and not the contributors as in "last comment is by contributor -> age out" so either contributor closes them say "not going to happen / this is bad" or contributor asks for changes and never gets replies, but not "we never looked at this PR, let's close it"

mrbobbytables commented 2 years ago

I did say for PRs, they should age out and never be frozen.

For issues, if they're a long term issue they can be frozen to avoid the stale bot.

EDIT: For PRs, its frequently abandoned by the author after a reviewer asks for changes and they just never come back. They should age out.

grosser commented 2 years ago

Yes, "abandoned PRs" should age out, but not "unreviewed PRs".

Debanitrkl commented 2 years ago

/area github-management

k8s-triage-robot commented 2 years ago

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:

You can:

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

/lifecycle stale

grosser commented 2 years ago

staying alive

k8s-triage-robot commented 2 years ago

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

This bot triages issues and PRs according to the following rules:

You can:

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

/lifecycle rotten

k8s-triage-robot commented 2 years ago

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

This bot triages issues and PRs according to the following rules:

You can:

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

/close

k8s-ci-robot commented 2 years ago

@k8s-triage-robot: Closing this issue.

In response to [this](https://github.com/kubernetes/community/issues/6232#issuecomment-1160059551): >The Kubernetes project currently lacks enough active 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/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 issue is closed > >You can: >- Reopen this issue or PR with `/reopen` >- Mark this issue or PR as fresh with `/remove-lifecycle rotten` >- Offer to help out with [Issue Triage][1] > >Please send feedback to sig-contributor-experience at [kubernetes/community](https://github.com/kubernetes/community). > >/close > >[1]: https://www.kubernetes.dev/docs/guide/issue-triage/ Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
grosser commented 2 years ago

/reopen

k8s-ci-robot commented 2 years ago

@grosser: Reopened this issue.

In response to [this](https://github.com/kubernetes/community/issues/6232#issuecomment-1160581176): >/reopen Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
k8s-triage-robot commented 2 years ago

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

This bot triages issues and PRs according to the following rules:

You can:

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

/close

k8s-ci-robot commented 2 years ago

@k8s-triage-robot: Closing this issue.

In response to [this](https://github.com/kubernetes/community/issues/6232#issuecomment-1190445106): >The Kubernetes project currently lacks enough active 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/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 issue is closed > >You can: >- Reopen this issue or PR with `/reopen` >- Mark this issue or PR as fresh with `/remove-lifecycle rotten` >- Offer to help out with [Issue Triage][1] > >Please send feedback to sig-contributor-experience at [kubernetes/community](https://github.com/kubernetes/community). > >/close > >[1]: https://www.kubernetes.dev/docs/guide/issue-triage/ Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.