kubernetes / kubernetes/community
Automation for GitHub Project Boards
- Dominant language
- Jupyter Notebook
- Stars
- 13k
- Forks
- 5.4k
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 29
Description
I currently run the [Node Triage Board](https://github.com/orgs/kubernetes/projects/49). We _manually_ update it based on [these guidelines](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-node/triage.md).
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
Contributor guide
Assessment
This issue has not been assessed yet.