Post Project Board Migration: REST API => GraphQL Part 2 of 2

[t-will-gillis]

Dependency

• [x] #6993

DRAFT notes- this issue may be moot.

Overview

Towards the end of GitHub's Sunset notice- Projects (classic) there is this note:

We need to determine how this will affect our GitHub Actions/ Workflows so that we can make changes where needed prior to the deadline.

Details

• Our workflows use a variety of calls to the GitHub API, for example a large number use the REST API v20 (c. 2020?), some use the REST API version 2022-11-28, and some use GraphQL.
• (???) Even if the upcoming November 19, 2024 deadline will not immediately affect us, we may want to have a roadmap to convert workflows using earlier API calls to GraphQL regardless, and
• (???) We may want to have a policy that all future workflows use GraphQL rather than the REST API. (???)

Action Items

• [ ] Create an issue to provide an overview about how our existing GraphQL queries are formatted, and determine whether HfLA should have a 'standard approach'.
• [ ] It is possible that we already have a standard approach (more or less), however in any case we should document this approach to make it easier for those unfamiliar with GraphQL to understand what the code is doing and write queries consistent with the existing queries.
• [ ] (???) Assuming that we do need to refactor REST API => GraphQL, workflows requiring changes:
  • [ ]

Resources/Instructions

• Sunset notice- Projects (classic)

[github-actions[bot]]

Hi @t-will-gillis.

Please don't forget to add the proper labels to this issue. Currently, the labels for the following are missing:

• Size

NOTE: Please ignore this comment if you do not have 'write' access to this directory.

To add a label, take a look at Github's documentation here.

Also, don't forget to remove the "missing labels" afterwards. To remove a label, the process is similar to adding a label, but you select a currently added label to remove it.

After the proper labels are added, the merge team will review the issue and add a "Ready for Prioritization" label once it is ready for prioritization.

Additional Resources:

• Wiki: How to create issues
• Wiki: How to read and interpret labels

[github-actions[bot]]

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 :)