Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
1 of 4 tasks
t-will-gillis opened this issue Jun 12, 2024 · 2 comments
Open
1 of 4 tasks

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

t-will-gillis opened this issue Jun 12, 2024 · 2 comments
Assignees
Labels
Complexity: Extra Large Draft Issue is still in the process of being created Feature: API Coding requires using an API Feature: Refactor GHA Refactoring GitHub actions to fit latest architectural norms Issue Making: Level 4 Create an Epic Issue, and it's Level 2 or 3 issues role: back end/devOps Tasks for back-end developers size: 8pt Can be done in 31-48 hours

Comments

@t-will-gillis
Copy link
Member

Dependency

DRAFT notes- this issue may be moot.

Overview

Towards the end of GitHub's Sunset notice- Projects (classic) there is this note:
Screenshot 2024-06-12 091646
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

@t-will-gillis t-will-gillis added role: back end/devOps Tasks for back-end developers Feature: Refactor GHA Refactoring GitHub actions to fit latest architectural norms Feature: API Coding requires using an API Issue Making: Level 4 Create an Epic Issue, and it's Level 2 or 3 issues Complexity: Extra Large labels Jun 12, 2024

This comment was marked as resolved.

@t-will-gillis t-will-gillis added size: 8pt Can be done in 31-48 hours Draft Issue is still in the process of being created and removed size: missing labels Jun 12, 2024
@t-will-gillis t-will-gillis self-assigned this Jun 12, 2024

This comment was marked as resolved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Complexity: Extra Large Draft Issue is still in the process of being created Feature: API Coding requires using an API Feature: Refactor GHA Refactoring GitHub actions to fit latest architectural norms Issue Making: Level 4 Create an Epic Issue, and it's Level 2 or 3 issues role: back end/devOps Tasks for back-end developers size: 8pt Can be done in 31-48 hours
Projects
Status: New Issue Approval
Development

No branches or pull requests

2 participants