Community: 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: https://github.com/kubernetes/test-infra/issues/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