From a29f75f43b66ab270e21a1adf45e07a1cdb566f1 Mon Sep 17 00:00:00 2001 From: Jordan Padams <33492486+jordanpadams@users.noreply.github.com> Date: Mon, 12 Oct 2026 08:50:16 -0700 Subject: [PATCH] fix: remove concurrency group from issue-project-automation.yml MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit GitHub Actions concurrency with cancel-in-progress: false only queues one waiting run at a time. When 3+ label events fire simultaneously a newer pending run cancels the older waiting one ("higher priority waiting request"), silently dropping intermediate events. GitHub Actions concurrency cannot queue more than one run — this is a platform limitation. The root race condition (concurrent read-merge-write of org field values) will be addressed at the script level instead. Refs: NASA-PDS/.github#29 Co-Authored-By: Claude Sonnet 4.6 --- .github/workflows/issue-project-automation.yml | 9 --------- 1 file changed, 9 deletions(-) diff --git a/.github/workflows/issue-project-automation.yml b/.github/workflows/issue-project-automation.yml index 9e257c8..52b3b6d 100644 --- a/.github/workflows/issue-project-automation.yml +++ b/.github/workflows/issue-project-automation.yml @@ -4,15 +4,6 @@ on: issues: types: [opened, labeled, unlabeled] -# Serialize all automation for a given issue. Selecting multiple labels in the UI fires -# one `labeled` event per label, each starting its own run; without this, concurrent runs -# race on the read-merge-write of org field values (see set_org_issue_field_values in -# NASA-PDS/.github) and can silently clobber each other's changes. Queue, don't cancel: -# every event still needs to be processed. -concurrency: - group: issue-automation-${{ github.repository }}-${{ github.event.issue.number }} - cancel-in-progress: false - jobs: # When an issue is opened, add it to default project(s) add-new-issue-to-project: