Automation for GitHub Project Boards

[ehashman]

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:

• Add cards to the Triage column automatically based on the search we use in the "Add Cards" query
• With maximum priority: All cards with any "do-not-merge/*" labels should be moved to the Waiting on Author column
• With next priority: All cards without [lgtm, needs-priority, needs-triage] should get moved to Needs Reviewer column
• With next priority: All cards without [needs-priority, needs-triage] and with lgtm should get moved to the Needs Approver column
• Move any reopened (previously closed) PRs back to the Triage column (this might already be possible)
• Move any PRs with "Changes Requested" reviews to the Waiting on Author column (might also be possible?)
• If a card was manually moved to a column, do not automatically move it without a label change occurring first (i.e. I don't want to fight automation when it's wrong)

/area github-management
/cc @mrbobbytables

[mrbobbytables]

/sig contributor-experience
/assign @mrbobbytables

[justaugustus]

Referencing the k/test-infra issue from back in the day: kubernetes/test-infra#9925

[mrbobbytables]

Just to update, the feedback has been passed onto GitHub 👍

[fabriziopandini]

+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

[lasomethingsomething]

+1. Brought up this issue yesterday during SIG Auth's first triage session.

[enj]

Can we use something like https://github.com/apps/project-bot in the interim?

[ehashman]

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.

[k8s-triage-robot]

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/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:

• 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

[ehashman]

/remove-lifecycle stale

This is still (painfully) relevant.