fix(enforce-single-assignee): add concurrency group#52
Merged
Conversation
Serializes workflow runs per issue so that when multiple `assigned` events fire simultaneously, only the first run acts. Subsequent runs see 0 assignees and exit early, preventing duplicate comments. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
scotwells
approved these changes
Mar 6, 2026
drewr
changed the title
drewr
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a concurrency group to the enforce-single-assignee workflow to prevent duplicate comments when multiple assignees are added simultaneously.
Problem
As shown in #50 and #51, when multiple users are assigned at once, GitHub fires one
assignedevent per user. Each concurrent workflow run posted its own comment, resulting in duplicates.Fix
Runs are now serialized per issue. The first run removes all assignees and posts one comment. Subsequent queued runs see 0 assignees and exit immediately with no action.