Open ehashman opened 3 years ago
/sig contributor-experience /assign @mrbobbytables
Referencing the k/test-infra issue from back in the day: https://github.com/kubernetes/test-infra/issues/9925
Just to update, the feedback has been passed onto GitHub 👍
+1 to this. Having some automation (add card, move card, remove card) based on configurable labels & issue/PR status would really help to start using project boards
+1. Brought up this issue yesterday during SIG Auth's first triage session.
Can we use something like https://github.com/apps/project-bot in the interim?
One additional ask: it would be an enormous improvement for columns to automatically sort by last updated (most recent at top, least recent at bottom for example). Right now, I have to look at every single issue in a column manually to see if it's been updated, about once a week.
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:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/remove-lifecycle stale
This is still (painfully) relevant.
Can we use something like https://github.com/apps/project-bot in the interim?
Sorry just saw this, it's no longer being maintained and doesn't work quite right these days :(
https://github.com/googleapis/repo-automation-bots could we use something like this, perhaps ? :eyes:
We can use https://github.com/alex-page/github-project-automation-plus and modify it according to our requirements.
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:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/remove-lifecycle stale
We can use https://github.com/alex-page/github-project-automation-plus and modify it according to our requirements.
There's quite a bit of modification required. In particular, we'd need to set up GH actions on any affected repos such as k/k and it doesn't support filtering by label.
/cc @hh
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:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
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:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
Revisit the issue, do we have any progress on this or we do have some standard configurations for project board. For sig scheduling, we recently create a new board for tracing, but not smooth enough. It's actually a hand-actuated. https://github.com/orgs/kubernetes/projects/79/views/1
/remove-lifecycle rotten
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:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/remove-lifecycle stale Any updates on this?
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
/lifecycle frozen
I currently run the Node Triage Board. We manually update it based on these guidelines.
The only automation available that works consistently is moving things to Done when closed or merged.
It would be great to have the support of automation to do the following tasks:
/area github-management /cc @mrbobbytables