chore: disable scheduled CI; run workflows on demand#5996
Merged
Conversation
ORM iteration has slowed enough that the high-frequency `check-for-update` poller (every 5 minutes) and the weekly cleanup / known-failing replays are no longer worth the CI spend. All three lose their `schedule:` triggers; `workflow_dispatch` is preserved so anyone can still run them manually from the Actions tab. The `schedule:` blocks are commented out (not deleted) so re-enabling is a one-PR uncomment when ORM iteration resumes. The README's CI status badge table previously embedded badges for `test` on four branches plus `check-for-update`. Without the schedule those badges would freeze at whatever colour they had on disable day, which risks broadcasting a stale-red status indefinitely. Replaced with a single sentence pointing to the Actions tab. Context: projects/disable-scheduled-ci/spec.md in prisma/prisma.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (1)
Summary by CodeRabbit
WalkthroughThree CI workflows (check-for-update, cleanup-clouds, failing-weekly) have their scheduled cron triggers commented out; manual ChangesOn-Demand CI Execution
🎯 1 (Trivial) | ⏱️ ~3 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
✨ Simplify code
Comment |
![coderabbitai[bot]](https://avatars.github.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@README.md`:
- Line 5: Update README.md to remove the contradictory “cron-based every 5
minutes” language and instead state that the check-for-update.yaml workflow is
triggered manually/on-demand; locate the section referencing
check-for-update.yaml (the paragraph around "check-for-update.yaml") and replace
the cron wording with instructions that workflows are triggered from the Actions
tab or via `gh workflow run`, and ensure the README consistently says CI runs
are manual/on-demand across both the earlier CI statement and the
check-for-update.yaml description.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro
Run ID: 2300b971-c51c-4194-b1a4-ba5b692c8142
📒 Files selected for processing (4)
.github/workflows/check-for-update.yaml.github/workflows/cleanup-clouds.yaml.github/workflows/failing-weekly.yamlREADME.md
Earlier in this PR the badge table was removed and the CI Status section gained an on-demand note, but the "Updates → Prisma" paragraph still described `check-for-update.yaml` as a 5-minute cron job. Rewrite that paragraph so it matches the rest of the README: the workflow runs on demand from the Actions tab or via `gh workflow run`.
aqrln
approved these changes
May 15, 2026
wmadden
added a commit
to prisma/prisma
that referenced
this pull request
May 15, 2026
## Summary Disables the `schedule:` triggers on the two scheduled test workflows in this repo so they stop spending CI minutes while ORM iteration is paused. They remain runnable on demand via `workflow_dispatch`. Also removes the cross-repo `Ecosystem Tests Status` badge from the README so it can't go stale-red after the corresponding schedule is disabled in `prisma/ecosystem-tests`. Workflows affected: - `.github/workflows/daily-test.yml` (was `0 4 * * 1-5`). - `.github/workflows/daily-buildpulse.yml` (was `*/30 3-4 * * *`). Not touched (intentionally): - `test.yml` — push/PR-driven; keeps running normally on `main`. - `codeql-analysis.yml` — security scans are cheap and stay. - `auto-close-github-discussions.yml`, `label-stale-issues.yml` — community housekeeping; negligible spend, stays. The `schedule:` blocks are commented out rather than deleted so re-enabling is a one-PR uncomment when ORM iteration resumes. ## Context Part of a coordinated effort across the Prisma ORM repos. Other PRs in flight: - `prisma/action-status-check#10` — pauses the daily Slack digest (deploys after merge). - `prisma/ecosystem-tests#5996` — disables `check-for-update`, `cleanup-clouds`, `failing-weekly`; removes the CI status badge table. - `prisma/language-tools` (next) — disables `1_check_for_updates`, `e2e_check_for_new_published_vsix`, `update-api-types`; removes the `e2e-vsix` badge. `prisma/prisma-engines` and `prisma/engines-wrapper` have no scheduled workflows. Full project spec: `projects/disable-scheduled-ci/spec.md` in this repo (transient — will be deleted at close-out). ## Verification - No workflow files are deleted; both modified workflows retain `workflow_dispatch:`. - README diff is limited to the two badge lines. ## To re-enable later For each workflow, uncomment its `schedule:` block. To restore the README badge, revert the README hunk of this commit. ## Acceptance criteria covered (from project spec) - AC1: no `schedule:` triggers remain on `daily-test.yml` or `daily-buildpulse.yml`. - AC4: each modified workflow still has `workflow_dispatch:`. - AC5: README no longer carries the `Ecosystem Tests Status` badge; `Prisma Tests Status` remains. - AC10: diff is limited to `schedule:` removal and the listed badge. - AC11: README sentence explains that scheduled CI is disabled and how it still runs.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Disables the
schedule:triggers on three workflows in this repo so they stop spending CI minutes while ORM iteration is paused. They remain runnable on demand viaworkflow_dispatch(Actions tab orgh workflow run).Workflows affected:
.github/workflows/check-for-update.yaml(was*/5 * * * *— by far the biggest spend in this repo)..github/workflows/cleanup-clouds.yaml(was weekly Mon)..github/workflows/failing-weekly.yaml(was weekly Sun).The
schedule:blocks are commented out rather than deleted so re-enabling is a one-PR uncomment when ORM iteration resumes.The README's CI status badge table is also removed. Without the
check-for-updatecron pushing new commits todev/latest/patch-dev/integration, thetestworkflow effectively stops running on those branches; their badges would freeze at whatever colour they had on disable day, which risks an indefinite stale-red signal on the repo home page. Replaced with a single sentence pointing to the Actions tab.Context
Part of a coordinated effort across the Prisma ORM repos. Other PRs in flight:
prisma/action-status-check#10— pauses the daily Slack digest first so this change doesn't trigger a noisy false-alarm.prisma/prisma(next) — disablesdaily-test.yml,daily-buildpulse.yml, and removes the cross-repoEcosystem Tests Statusbadge from the README.prisma/language-tools(next) — disables1_check_for_updates.yml,e2e_check_for_new_published_vsix.yml,update-api-types.yml, and removes thee2e-vsixbadge from the README.Full project spec:
projects/disable-scheduled-ci/spec.mdinprisma/prisma(transient — will be deleted at close-out).Verification
workflow_dispatch:.To re-enable later
For any individual workflow, uncomment its
schedule:block. To restore the README badge table, revert the README hunk of this commit.Acceptance criteria covered (from project spec)
schedule:triggers remain on the three in-scope workflow files.workflow_dispatch:.prisma/ecosystem-testsREADME no longer contains the CI Status badge table.schedule:removal and the listed badge block.