rapidsai / rapidsai/shared-workflows

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

Open
#277 2 comments 0 reactions 1 assignee View on GitHub

@jarmak-nv is already working on this.

Since Feb 24, 2025.

Dominant language
Shell
Stars
8
Forks
33
Avg merge
23h 51m
Merged PRs (30d)
19

Description

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

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.