We have Project boards to track the development of Intern and it's next couple of versions. Those boards should be automated so they'll stay relevant. GitHub's built-in automation is good for simple cases, but not really for how we want to use the boards.
Expected behavior:
New, unassigned issues go to “Triage” (general dev board; issues will be manually added to the version boards)
Unassigned issues with priority and effort labels go to "To do" (general dev board)
Newly assigned issues that are in "To do" or "Triage" go to “In progress”
“To do” issues that are assigned go to “In progress”
“In progress” issues that are de-assigned go back to “To do”
Issues that are on the board and are closed go to “Done”
Closed issues on the board that are re-opened go back to “In progress”
When issues are added to a column, they should be added in priority order, with priority-high at the top and priority-low at the bottom.
Only issues go on the board, not PRs. PRs will be accessible through issue links.
We have Project boards to track the development of Intern and it's next couple of versions. Those boards should be automated so they'll stay relevant. GitHub's built-in automation is good for simple cases, but not really for how we want to use the boards.
Expected behavior:
priority-highat the top andpriority-lowat the bottom.A repo has been created at https://github.com/theintern/action-project-manager to host a GitHub Action for this.