Repository navigation
chore(ci): High Actions usage from Squad Heartbeat (Ralph) – recommendation to remove scheduled trigger (or make config option on squad init) #815
Description
Problem
The GitHub Actions usage for this repository is extremely high, with the Squad Heartbeat (Ralph) workflow accounting for a large number of workflow runs.
Root cause
- The Squad Heartbeat (Ralph) workflow is currently set to run on a schedule: every 30 minutes (cron: '*/30 * * * *').
- In combination with its event-based triggers (issue closed/labeled, PR closed), this causes frequent workflow runs regardless of whether there is actual triage needed.
- Given the frequency (48 times/day, every day), this results in significant Actions minute consumption, even though each run is relatively lightweight.
Impact
- Rapid consumption of GitHub Actions minutes.
- Possible throttling or high billing for Actions usage.
- Many runs do not actually "triage" anything because they are on a timer, not in response to real repo events.
Recommendation
Remove the scheduled trigger and switch to an event-driven approach. Or; make two options that can be configured on squad init to use either the current functionality or the proposed lighter version.
Specific change
Replace this block in .github/workflows/squad-heartbeat.yml:
on:
schedule:
- cron: '*/30 * * * *'
issues:
types: [closed, labeled]
pull_request:
types: [closed]
workflow_dispatch:
With this:
on:
issues:
types: [opened, labeled, closed]
pull_request:
types: [closed]
workflow_dispatch:
- This keeps the workflow fully reactive to meaningful project board changes, but eliminates the constant polling.
- It is strongly recommended to update all synced copies:
- templates/workflows/squad-heartbeat.yml
- packages/squad-cli/templates/workflows/squad-heartbeat.yml
- .squad/templates/workflows/squad-heartbeat.yml
- .github/workflows/squad-heartbeat.yml
Expected Result
- Drastically fewer workflow runs for Squad Heartbeat (Ralph).
- No loss of actual automation for issue triage, Copilot assignment, or board management.
- Significant reduction in Actions billing/minute usage.
- Espcially impactful for users who are on personal plans.
Activity
[-]High Actions usage from Squad Heartbeat (Ralph) – recommendation to remove scheduled trigger (or make config option on squad init)[/-][+]chore(ci): High Actions usage from Squad Heartbeat (Ralph) – recommendation to remove scheduled trigger (or make config option on squad init)[/+]fix: add issues:opened trigger to squad-heartbeat workflow
github-actions commentedon Apr 8, 2026
🏗️ Squad Triage — Flight (Lead)
Issue: #815 — chore(ci): High Actions usage from Squad Heartbeat (Ralph) – recommendation to remove scheduled trigger (or make config option on squad init)
Assigned to: Flight (Lead)
Reason: No specific domain match — assigned to Lead for further analysis
@copilot evaluation: No strong capability match — routed to squad member.
Team roster:
squad:flightsquad:proceduressquad:eecomsquad:fidosquad:paosquad:capcomsquad:controlsquad:surgeonsquad:boostersquad:gncsquad:networksquad:retrosquad:incosquad:guidosquad:telemetrysquad:voxsquad:dskysquad:simssquad:handbooksquad:ralphsquad:copilotfix: add issues:opened trigger to squad-heartbeat workflow
bradygaster commentedon Apr 18, 2026
We've mentioned this in a few other issues, and we've since removed the
cronitems from the workflows. Apologies for this. We've also added the--no-workflowsswitch for folks who don't use Ralph's actions/workflows.