ci: pause schedules of 9 idle workflows (LLM spend and noise) - #4992
Conversation
main has not changed since 2026-06-25 but these kept running: sourcing (fails every run after paying for batch 1), scheduled-maintenance, sourcing-recheck, flagship-curate, improve-pipeline-baseline (LLM spend), and ci-pr-health, job-worker, auto-merge-backfill, auto-rebase (noise or idle runner time). workflow_dispatch still works; backups, exports, snapshots and health monitors are untouched. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01WXiHX1a9DEuvwydgTP43ZE
Protected paths modifiedThis PR modifies files that affect agent behavior, CI, or validation rules. Modified protected files:
|
|
Warning Review limit reachedNext included review available in 45 minutes. View limit detailsLimit details: You’ve used the included review currently available. You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Review configuration: ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (9)
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. Comment |
Test Coverage Report
Coverage is advisory only — no thresholds enforced. Generated by |
mainhas not changed since 2026-06-25, butAUTOMATION_PAUSEDisfalseand about 20 cron workflows keep running against it. This PR comments out theschedule:block of the nine that spend LLM money or only produce noise.workflow_dispatchstill works on all of them, and nothing else changes.sourcing.ymlAll customId values must be unique within a batchscheduled-maintenance.ymlsourcing-recheck.yml,flagship-curate.ymlimprove-pipeline-baseline.ymlci-pr-health.ymlci.ymlis "stale" (nothing pushed); reopens a Linear ticket each timejob-worker.ymlauto-merge-backfill.ymlauto-rebase.ymlKept running: database backup, wiki-server export, resource snapshots, data validation, render monitor, health checks, the dead-man switch, entity/fact sync. The only thing that watches these schedules is
crux health --check=actions, which itself runs insideci-pr-health, so no other alarm fires.To resume any workflow, uncomment its
schedule:lines (each has a dated note).🤖 Generated with Claude Code
https://claude.ai/code/session_01WXiHX1a9DEuvwydgTP43ZE
Generated by Claude Code