You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
Dependency
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
Action Items
Resources/Instructions
The text was updated successfully, but these errors were encountered: