ci: implement concurrency controls for the sync-prs-to-next workflow

[hesxo]

Add workflow-level concurrency to sync-prs-to-next to prevent overlapping runs. In-progress runs are canceled when a newer run starts for the same PR/workflow context, reducing duplicate sync attempts and contention.

Summary by CodeRabbit

• Chores
  • Improved sync workflow reliability with dynamic concurrency control that automatically cancels redundant background processes and prevents extended execution times.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 2e453e92-b4ed-41ad-bb2e-c5d2b246094a

📥 Commits

Reviewing files that changed from the base of the PR and between f0d4afa and 0a93651.

📒 Files selected for processing (1)

• .github/workflows/sync-prs-to-next.yml

---

Walkthrough

Added workflow-level concurrency control to the sync-prs-to-next GitHub Actions workflow with dynamic group selection based on workflow run ID, pull request number, or branch reference. Configured in-flight run cancellation and enforced a 20-minute timeout on the sync job.

Changes

Cohort / File(s)	Summary
Workflow Configuration .github/workflows/sync-prs-to-next.yml	Added concurrency control with dynamic group selection and cancel-in-progress: true to prevent duplicate runs. Set timeout-minutes: 20 on the sync job to bound execution time.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Poem

🐰 A workflow so swift, now bounded with care,
With concurrency locks floating through the air,
Duplicate runs shall not reign,
Twenty minutes—no strain,
Efficient syncing beyond compare! ✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and specifically describes the main change: implementing concurrency controls for the sync-prs-to-next workflow, which matches the file modified and the core objective of preventing overlapping runs.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[hesxo]

@maintainers

This is a low risk improvement that fixes a real issue in the current workflow.

Right now, multiple sync jobs can run at the same time, which can cause duplicate PR syncs and occasional conflicts. This change ensures only the latest run executes and cancels the rest.

No logic changes, no impact to functionality only stabilizes the workflow and reduces unnecessary CI usage.

All checks are passing. Safe to merge.