How to Turn Off Unused Scheduled CI Jobs

A nightly cron for a report nobody reads still runs every night, quietly billing minutes forever.

Scheduled workflows outlive the need that created them. A nightly job for a deprecated dashboard keeps firing on the default branch indefinitely. Auditing schedules and disabling the dead ones removes pure recurring waste.

Steps

• List every workflow with an on.schedule trigger.
• Check last-run usefulness with each owner; confirm nobody reads the output.
• Disable the workflow (or remove the schedule) rather than leaving it firing.

Find and disable schedules

# List scheduled workflows
grep -rl "schedule:" .github/workflows

# Disable one whose output is no longer used
gh workflow disable nightly-legacy-report.yml

Tradeoffs

• Disable rather than delete first, so you can re-enable if it turns out to matter.
• Some schedules warm caches or catch drift; confirm the job is truly unused before cutting it.

Related guides