fix(action): Honor PR trigger parallelism#325
Merged
Conversation
Run matched PR triggers through the configured concurrency pool instead of fanning out every matched trigger at once. This makes the action-level parallel input and runner concurrency apply to trigger dispatch as documented. Add regression coverage that holds the first matched trigger open and verifies a second trigger is not dispatched when parallel is set to 1. Fixes GH-323 Co-Authored-By: GPT-5 Codex <noreply@anthropic.com>
f898e30 to
b41caf9
Compare
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
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.
Matched PR triggers now run through the configured concurrency pool instead of fanning out all matched triggers at once. This makes the Action parallel input and runner concurrency setting serialize trigger execution when set to 1, while preserving the existing file-level semaphore inside running triggers.
Concurrency Docs
Document runner.concurrency and clarify the split between Action and CLI behavior: GitHub Actions use the setting for matched trigger dispatch and file analysis, while CLI --parallel gates file analysis across running skills.
Adds deterministic regression coverage for multiple matched triggers.
Fixes #323