ci: disable all cron schedules to stop burning Actions minutes

[jeremylongshore]

Summary

• Comment out schedule: / cron: triggers in all 4 workflow files that had them
• Each workflow retains workflow_dispatch so they can still be triggered manually
• Affected workflows:
  • auto-fix-budget.yml (was hourly 0 * * * *)
  • auto-fix-monitor.yml (was every 6h 0 */6 * * *)
  • auto-fix-report.yml (was weekly Monday 9am 0 9 * * 1)
  • drift-detection.yml (was weekly Sunday midnight 0 0 * * 0)

Test plan

• Verify CI passes (YAML remains valid with workflow_dispatch as the only trigger)
• Confirm no scheduled runs appear after merge

🤖 Generated with Claude Code

Summary by CodeRabbit

• Chores
  • Disabled scheduled automation for background workflows; these operations now require manual triggering only. Existing manual trigger capabilities remain unchanged.

[gemini-code-assist]

Note

Gemini is unable to generate a summary for this pull request due to the file types involved not being currently supported.

[greptile-apps]

Your free trial has ended. If you'd like to continue receiving code reviews, you can add a payment method here.

[qodo-code-review]

Review Summary by Qodo

Disable cron schedules to reduce Actions minutes

✨ Enhancement

Walkthroughs

Description

• Disable all cron schedules across 4 workflows
• Preserve manual trigger capability via workflow_dispatch
• Reduce GitHub Actions minutes consumption
• Workflows affected: auto-fix-budget, auto-fix-monitor, auto-fix-report, drift-detection

Diagram

flowchart LR
  A["4 Workflow Files"] -- "Comment out schedule triggers" --> B["Cron disabled"]
  B -- "Retain workflow_dispatch" --> C["Manual trigger only"]
  C -- "Reduce cost" --> D["Lower Actions usage"]

Loading

File Changes

1. .github/workflows/auto-fix-budget.yml ⚙️ Configuration changes +4/-3

Disable hourly budget monitoring schedule

• Commented out hourly cron schedule (0 * * * *)
• Added explanatory comment about disabling
• Preserved workflow_dispatch manual trigger

.github/workflows/auto-fix-budget.yml

---

2. .github/workflows/auto-fix-monitor.yml ⚙️ Configuration changes +4/-3

Disable 6-hourly health monitor schedule

• Commented out 6-hourly cron schedule (0 */6 * * *)
• Added explanatory comment about disabling
• Preserved workflow_dispatch manual trigger

.github/workflows/auto-fix-monitor.yml

---

3. .github/workflows/auto-fix-report.yml ⚙️ Configuration changes +4/-3

Disable weekly performance report schedule

• Commented out weekly Monday cron schedule (0 9 * * 1)
• Added explanatory comment about disabling
• Preserved workflow_dispatch manual trigger

.github/workflows/auto-fix-report.yml

---

View more (1)

4. .github/workflows/drift-detection.yml ⚙️ Configuration changes +4/-3

Disable weekly drift detection schedule

• Commented out weekly Sunday cron schedule (0 0 * * 0)
• Added explanatory comment about disabling
• Preserved workflow_dispatch manual trigger

.github/workflows/drift-detection.yml

---

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (1) 📘 Rule violations (0) 📎 Requirement gaps (0)

1. Unreachable notification job 🐞 Bug ✧ Quality

Description

After removing the schedule trigger from auto-fix-budget.yml, the notify-on-critical job can
never run because it is explicitly gated to github.event_name == 'schedule'. This silently
disables critical notifications for any failing manual run (and for all runs going forward unless
schedule is re-enabled).

Code

.github/workflows/auto-fix-budget.yml[R3-8]

on:
-  schedule:
-    # Run every hour to track budget in near real-time
-    - cron: '0 * * * *'
+  # schedule disabled — burns Actions minutes
+  # schedule:
+  #   # Run every hour to track budget in near real-time
+  #   - cron: '0 * * * *'
  workflow_dispatch: # Allow manual trigger

Evidence

The workflow no longer has a schedule trigger (only workflow_dispatch remains), yet the
notification job still requires the event to be schedule, making the job unreachable.

.github/workflows/auto-fix-budget.yml[3-8]
.github/workflows/auto-fix-budget.yml[157-161]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
`notify-on-critical` is now dead code: the workflow no longer triggers via `schedule`, but the job still requires `github.event_name == 'schedule'`.

### Issue Context
This PR comments out the `schedule:` trigger and keeps only `workflow_dispatch`. Any remaining conditions checking for the `schedule` event will never be true.

### Fix Focus Areas
- .github/workflows/auto-fix-budget.yml[3-8]
- .github/workflows/auto-fix-budget.yml[157-161]

### Suggested change
Pick one of these (depending on intended behavior):
1. If notifications should work for manual runs too: change to `if: failure()` (or `if: failure() && github.event_name == 'workflow_dispatch'`).
2. If notifications are intentionally disabled while schedules are off: remove the `notify-on-critical` job entirely to avoid misleading configuration.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

ⓘ The new review experience is currently in Beta. Learn more

[coderabbitai]

Caution

Review failed

Pull request was closed or merged during review

📝 Walkthrough

Walkthrough

Four GitHub Actions workflows are modified to disable automatic scheduled triggers by commenting out cron schedule entries while preserving manual workflow_dispatch invocation. No changes to workflow steps or logic. Consistent modifications across all workflows, with identical line counts.

Changes

Cohort / File(s)	Summary
Disabled Scheduled Triggers .github/workflows/auto-fix-budget.yml, .github/workflows/auto-fix-monitor.yml, .github/workflows/auto-fix-report.yml, .github/workflows/drift-detection.yml	Disabled automatic cron-based triggers across all four workflows by commenting out schedule blocks. Manual workflow_dispatch trigger remains active for each. Modification aligns with conserving GitHub Actions minutes. Each file modified with +4/-3 lines.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

Poem

🐰 With schedules now silent, we hop with delight,
No hourly scurrying through the dead of night,
Manual triggers shall guide our way,
Conserving our actions, hooray, hooray! ✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely summarizes the main change: disabling cron schedules across workflows to conserve GitHub Actions minutes.
Description check	✅ Passed	The description covers the summary and test plan sections well, but is missing several required template sections like Type of Change, Breaking Changes, and Security Considerations.
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
• Post copyable unit tests in a comment
• Commit unit tests in branch ci/disable-cron-schedules

---

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.}