[PR #214] ci: add concurrency guard to gh-combined-tasks cron to stop overlapping runs #212

New issue

Open

opened 2026-10-27 21:10:40 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-27 21:10:40 +00:00

Owner

📋 Pull Request Information

Original PR: https://github.com/Comfy-Org/Comfy-PR/pull/214
Author: @claude[bot]
Created: 9/14/2026
Status: 🔄 Open

Base: main ← Head: fix/gh-combined-tasks-concurrency-guard

📝 Commits (1)

fb27e42 ci: add concurrency guard to gh-combined-tasks cron to stop overlapping runs

📊 Changes

1 file changed (+4 additions, -0 deletions)

View changed files

📝 .github/workflows/gh-combined-tasks.yaml (+4 -0)

📄 Description

Requested via Slack thread

Before: gh-combined-tasks.yaml (the cron running 14 GitHub-polling tasks, including the #frontend release notifier) has no concurrency guard. When a run gets stuck on GitHub API rate limits and hits the 10-minute step timeout, the next 5-minute cron tick fires anyway and piles more requests onto the same token — compounding the rate-limit exhaustion instead of letting it recover. This has caused 40+ consecutive failed runs.

After: a concurrency group with cancel-in-progress: true means a new run cancels any still-running previous one instead of stacking on top of it, so the token gets a chance to recover between attempts.

This does not fix the underlying rate-limit exhaustion itself (that needs someone with token access to check gh api rate_limit and possibly reduce polling frequency or split up the 14 bundled tasks) — it just stops the pile-up that's making it worse.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/Comfy-Org/Comfy-PR/pull/214 **Author:** [@claude[bot]](https://github.com/apps/claude) **Created:** 9/14/2026 **Status:** 🔄 Open **Base:** `main` ← **Head:** `fix/gh-combined-tasks-concurrency-guard` --- ### 📝 Commits (1) - [`fb27e42`](https://github.com/Comfy-Org/Comfy-PR/commit/fb27e42cfd42e24e9859dc4729f5d747c6ed4406) ci: add concurrency guard to gh-combined-tasks cron to stop overlapping runs ### 📊 Changes **1 file changed** (+4 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `.github/workflows/gh-combined-tasks.yaml` (+4 -0) </details> ### 📄 Description  _Requested via [Slack thread](https://comfy-organization.slack.com/archives/C075ANWQ8KS/p1789177564972699?thread_ts=1789177564.972699&cid=C075ANWQ8KS)_ **Before:** `gh-combined-tasks.yaml` (the cron running 14 GitHub-polling tasks, including the #frontend release notifier) has no `concurrency` guard. When a run gets stuck on GitHub API rate limits and hits the 10-minute step timeout, the next 5-minute cron tick fires anyway and piles more requests onto the same token — compounding the rate-limit exhaustion instead of letting it recover. This has caused 40+ consecutive failed runs. **After:** a `concurrency` group with `cancel-in-progress: true` means a new run cancels any still-running previous one instead of stacking on top of it, so the token gets a chance to recover between attempts. This does not fix the underlying rate-limit exhaustion itself (that needs someone with token access to check `gh api rate_limit` and possibly reduce polling frequency or split up the 14 bundled tasks) — it just stops the pile-up that's making it worse. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

bsakaguchi added the

pull-request

label

2026-10-27 21:10:40 +00:00

bsakaguchi referenced this issue

2026-10-27 21:10:40 +00:00

[PR #212] [MERGED] Backport checker: don't flag dual-homed commits as needing backport #213