Repository navigation
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.
feat(concurrency): add per-repo serialized concurrency to dev-lead stubs #322
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Uh oh!
There was an error while loading. Please reload this page.
feat(concurrency): add per-repo serialized concurrency to dev-lead stubs #322
Changes from all commits
7d57c04File filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
With this repository-wide
dev-leadconcurrency group, bursts of non-check_runevents are not fully serialized: GitHub Actions defaults to only one pending run per concurrency group, so a third PR comment/review/label orrepository_dispatchwhile one run is active cancels and replaces the earlier pending dev-lead run rather than executing it later (GitHub docs). That means some requested dev-lead work can be silently dropped under load; addqueue: maxwithcancel-in-progress: falseif the intent is to run every event one at a time.Useful? React with 👍 / 👎.