Skip to content

ci: Use GH concurrency queue instead of turnstile in pr-is-up-to-date.yml#49057

Open
anomiex wants to merge 1 commit into
trunkfrom
update/ci-pr-is-up-to-date-replace-turnstile
Open

ci: Use GH concurrency queue instead of turnstile in pr-is-up-to-date.yml#49057
anomiex wants to merge 1 commit into
trunkfrom
update/ci-pr-is-up-to-date-replace-turnstile

Conversation

@anomiex
Copy link
Copy Markdown
Contributor

@anomiex anomiex commented May 21, 2026

Proposed changes

GitHub has recently added the ability to have an actual queue (max 100 entries) for its concurrency feature. This should perform better than turnstile, so let's try it out.

Also, there's a bit of cruft in the file: when I originally wrote it, I thought of it as one feature so I put it all in one file, and then had to get a bit hacky to avoid always having a skipped job in the PR check list. But we can also avoid that, more cleanly, by just having two independent workflows.

Related product discussion/links

p1779371671037339-slack-C05Q5HSS013

Does this pull request change what data or activity we track or use?

No

Testing instructions

….yml

GitHub has recently added the ability to have an actual queue (max 100
entries) for its concurrency feature. This should perform better than
turnstile, so let's try it out.

Also, there's a bit of cruft in the file: when I originally wrote it, I
thought of it as one feature so I put it all in one file, and then had
to get a bit hacky to avoid always having a skipped job in the PR check
list. But we can also avoid that, more cleanly, by just having two
independent workflows.
@anomiex anomiex self-assigned this May 21, 2026
@anomiex anomiex requested a review from a team as a code owner May 21, 2026 15:07
@anomiex anomiex added [Status] Needs Review This PR is ready for review. [Pri] Normal labels May 21, 2026
@github-actions github-actions Bot added the Actions GitHub actions used to automate some of the work around releases and repository management label May 21, 2026
@github-actions
Copy link
Copy Markdown
Contributor

Thank you for your PR!

When contributing to Jetpack, we have a few suggestions that can help us test and review your patch:

  • ✅ Include a description of your PR changes.
  • ✅ Add a "[Status]" label (In Progress, Needs Review, ...).
  • ✅ Add testing instructions.
  • ✅ Specify whether this PR includes any changes to data or privacy.
  • ✅ Add changelog entries to affected projects

This comment will be updated as you work on your PR and make changes. If you think that some of those checks are not needed for your PR, please explain why you think so. Thanks for cooperation 🤖


Follow this PR Review Process:

  1. Ensure all required checks appearing at the bottom of this PR are passing.
  2. Make sure to test your changes on all platforms that it applies to. You're responsible for the quality of the code you ship.
  3. You can use GitHub's Reviewers functionality to request a review.
  4. When it's reviewed and merged, you will be pinged in Slack to deploy the changes to WordPress.com simple once the build is done.

If you have questions about anything, reach out in #jetpack-developers for guidance!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Actions GitHub actions used to automate some of the work around releases and repository management [Pri] Normal [Status] Needs Review This PR is ready for review.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant