Complete ProjectV2 automations when GitHub supports them

[andrewvaughan]

Description

GitHub had a huge oversight when disabling Classic Projects and not supporting V2 Projects in GitHub Actions. As such, these automations could not be implemented and must be done manually during the SDLC. These should be added when and if GitHub finally gets around to meeting their established functionality with V1 projects.

This is an extension from Issue #23, so that other automation functionality would not be blocked.

Relevant references:

• https://github.com/orgs/community/discussions/17405#discussioncomment-2940411
• https://github.com/orgs/community/discussions/84050 (Projects community)
• https://github.com/orgs/community/discussions/62113 (Actions community)

Although GitHub seems to not be interacting with the community much, I don't expect this to be fixed any time soon...

---

Issue moves to Approved for Development

• Remove the Needs Triage label
• Add the Help Wanted label, if no user assigned
• Add the Needs Release Assignment label, if no milestone set
• Transition the Request: ... label to the appropriate Type: ... label
• Add a warning if no Request: ... or Type: ... label exists
• If a Wontfix label is on the Issue, add a warning comment

Issue moves to In Progress

• Remove the Needs Triage label
• Add the Help Wanted label and a warning, if no user assigned
• Add the Needs Release Assignment label and a warning, if no milestone assigned
• Transition the Request: ... label to the appropriate Type: ... label
• Add a warning if no Request: ... or Type: ... label exists
• Add a warning if a Wontfix: ... label exists
• Add a warning if no Project Points or Priority are set

Issue moves to Code Review

• Remove the Needs Triage label
• Add the Help Wanted label and a warning, if no user assigned
• Add the Needs Release Assignment label and a warning, if no milestone assigned
• Transition the Request: ... label to the appropriate Type: ... label
• Add a warning if no Request: ... or Type: ... label exists
• Add a warning if a Wontfix: ... label exists
• Add a warning if no Project Points or Priority are set
• If moved via the board (i.e., not a Pull Request) add a warning about needing a PR

Issue moves to Pending Deployment

• Remove the Needs Triage label
• Add the Help Wanted label and a warning, if no user assigned
• Add the Needs Release Assignment label and a warning, if no milestone assigned
• Transition the Request: ... label to the appropriate Type: ... label
• Add a warning if no Request: ... or Type: ... label exists
• Add a warning if a Wontfix: ... label exists
• Add a warning if no Project Points or Priority are set
• If moved via the board (i.e., not a main Pull Request acceptance) add a warning about needing a PR

Issue moves to User Acceptance Testing

• Remove the Needs Triage label
• Add the Help Wanted label and a warning, if no user assigned
• Add the Needs Release Assignment label and a warning, if no milestone assigned
• Transition the Request: ... label to the appropriate Type: ... label
• Add a warning if no Request: ... or Type: ... label exists
• Add a warning if a Wontfix: ... label exists
• Add a warning if no Project Points or Priority are set
• If moved via the board (i.e., not a staging Pull Request acceptance) add a warning about needing a PR

Issue moves to Done

• Remove the Needs Triage label
• Add the Help Wanted label and a warning, if no user assigned
• Add the Needs Release Assignment label and a warning, if no milestone assigned
• Transition the Request: ... label to the appropriate Type: ... label
• Add a warning if no Request: ... or Type: ... label exists
• Add a warning if a Wontfix: ... label exists
• Add a warning if no Project Points or Priority are set
• If moved via the board (i.e., not a production Pull Request acceptance) add a warning about needing a PR

Issue moves to Parking Lot

• Remove the Needs Triage label
• Remove the Help Wanted label
• Remove any assigned user
• Remove any assigned milestone
• If a Pull Request with this Issue engaged is open, add a warning

Examples

No response

Priority

None

Additional context

No response

Code of Conduct

• I agree to follow this project's Code of Conduct