summary refs log tree commit diff
path: root/.github/workflows/triage-incoming.yml
diff options
context:
space:
mode:
authorKat Gerasimova <ekaterinag@element.io>2022-08-25 12:09:23 +0100
committerGitHub <noreply@github.com>2022-08-25 12:09:23 +0100
commita2824465027c9036b98e56a52b53c80ca2aaa71b (patch)
treef1aa04c465a8bff60225bdab8dcfe7a44ba5d78a /.github/workflows/triage-incoming.yml
parentComment about a better future where we can get the state diff between two eve... (diff)
downloadsynapse-a2824465027c9036b98e56a52b53c80ca2aaa71b.tar.xz
Update automation for incoming issues (#13629)
GitHub appears to be deprecating addProjectNextItem by not allowing it to be used alongside projectV2 to get the project ID, so switching to using addProjectV2ItemById instead.
Diffstat (limited to '.github/workflows/triage-incoming.yml')
-rw-r--r--.github/workflows/triage-incoming.yml8
1 files changed, 4 insertions, 4 deletions
diff --git a/.github/workflows/triage-incoming.yml b/.github/workflows/triage-incoming.yml
index 8467970128..f926bcb759 100644
--- a/.github/workflows/triage-incoming.yml
+++ b/.github/workflows/triage-incoming.yml
@@ -14,13 +14,13 @@ jobs:
         with:
           headers: '{"GraphQL-Features": "projects_next_graphql"}'
           query: |
-            mutation add_to_project($projectid:ID!,$contentid:ID!) {
-              addProjectNextItem(input:{projectId:$projectid contentId:$contentid}) {
-                projectNextItem {
+              mutation add_to_project($projectid:ID!,$contentid:ID!) {
+                addProjectV2ItemById(input: {projectId: $projectid contentId: $contentid}) {
+                item {
                   id
+                  }
                 }
               }
-            }
           projectid: ${{ env.PROJECT_ID }}
           contentid: ${{ github.event.issue.node_id }}
         env: