Skip to content

fix: rename new gql field to better reflect what it is #37622

fix: rename new gql field to better reflect what it is

fix: rename new gql field to better reflect what it is #37622

Triggered via pull request August 14, 2024 13:03
Status Success
Total duration 17s
Artifacts

project_management.yml

on: pull_request
Linked Issues & Project Board Automation
5s
Linked Issues & Project Board Automation
Verify CHANGELOG Updated
0s
Verify CHANGELOG Updated
Fit to window
Zoom out
Zoom in

Annotations

1 warning
Linked Issues & Project Board Automation
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/[email protected]. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/