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.

Sign up for GitHub

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

Jump to bottom

[BUG(?)] Have `project-get-set-iteration-field.yaml` not fail after linked issue is updated #277

Open

mroeschke opened this issue Feb 7, 2025 · 0 comments

mroeschke commented Feb 7, 2025

I believe if a PR links an invalid/incorrectly formatted(?) issue, this workflow will fail with

gh: The iteration Id does not belong to the field
{"data":{"updateProjectV2ItemFieldValue":null},"errors":[{"type":"VALIDATION","path":["updateProjectV2ItemFieldValue"],"locations":[{"line":3,"column":9}],"message":"The iteration Id does not belong to the field"}]}

and even if the linked issue is corrected, this job will continue to fail

e.g.

https://github.com/rapidsai/cudf/actions/runs/13145770622/job/36683471245?pr=17760
https://github.com/rapidsai/cudf/actions/runs/13207892718/job/36875291888?pr=17954

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment