Post PBB migration: Refactor "Move Closed Issues" workflow

[t-will-gillis]

Dependency

• Post PBB migration: Refactor "Issue Trigger"  #7075

Overview

The new Projects Beta is structured a little differently from Projects (classic). During to our recent migration from Projects (classic) to Projects Beta, we scrubbed our workflows and removed all functionality that referenced 'columns' as this term is no longer used. We need to refactor our post migration workflows so that they have similar functionality as previously.

Details

The move-closed-issues.yaml file is triggered when an issue is closed. It reviews which labels are on the issue, and prior to migration to Projects Beta, issues with a particular label were assigned to the "QA" column. This file's logic needs to be rewritten in terms of the 'status' field instead, using GraphQL.

Action Items

• This issue involves GithHub Actions and GraphQL. You will need the new Project Board Beta set up in your repo so that you are able to test and demonstrate your solution. Refer to the "Resources/Instructions" section below to get started, and be sure to let us know if you have questions.
• In move-closed-issues.yaml, refactor the code using GraphQL so that specific issues are sorted to the appropriate 'status' of "Done" or "QA".
• Note that sort-closed-issues.js already has the conditionals in place and are reporting the correct final 'status' for each closed issue. Also note that Projects Beta automatically sorts all closed issues to "QA" status.
• What remains is to use GraphQL to sort the appropriate issues to "QA" status:
  • One option is to do this after the automatic workflow has moved all issues to "QA" so that there is no conflict.
  • Another option is to remove the automatic workflow sort for the closed issues, and instead have move-closed-issues.yaml do all of the sorting.
• Note also that the intent is that you will use existing modules wherever possible. These include:
  • /utils/query-issue-info.js
  • /utils/_data/status-field-ids
  • /utils/mutate-issue-status.js
  • Feel free to make edits and/or suggestions as long as these will work with the existing codebase.
• Test in your repo and demonstrate that your solution works.

Resources/Instructions

• Initial GraphQL queries and results
• GitHub GraphQL Explorer
• GitHub GraphQL API
• Hack for LAs GitHub Actions
• Pre-migration issues:
  • PR PBB migration "Move Closed Issues" #7056 fixes Project Board Migration: refactoring of "Move Closed Issues" workflow #7039
• This issue initiated by Prep for Project Board Migration: GitHub Actions / Workflows Part 1 of 2  #6993

[github-actions]

Hi @t-will-gillis, thank you for taking up this issue! Hfla appreciates you :)

Do let fellow developers know about your:-
i. Availability: (When are you available to work on the issue/answer questions other programmers might have about your issue?)
ii. ETA: (When do you expect this issue to be completed?)

You're awesome!

P.S. - You may not take up another issue until this issue gets merged (or closed). Thanks again :)