[cleanup][ci] Disable daily scheduled CI runs to preserve Actions budget - #41
Merged
Merged
Conversation
Praveenkumar76
changed the title
Praveenkumar76
changed the title
Srinathc
approved these changes
Jun 22, 2026
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.
CI Optimization
Motivation
Our repository fork inherited multiple upstream Apache Pulsar cron jobs. These automated jobs (CI, Flaky Tests, Gradle Cache updates, and CodeQL) run multiple times a day/week, rapidly draining our internal GitHub Actions quota even when no active development is happening.
Modifications
Commented out the
scheduleblock inside.github/workflows/pulsar-ci.yaml.github/workflows/pulsar-ci-flaky.yaml.github/workflows/ci-gradle-cache-update.yaml.github/workflows/codeql.yamlto permanently disable the automated daily runs,Example:
cron: '0 12 * * *')cron: '0 6 * * *')Standard PR triggers (
pull_request) and manual triggers (workflow_dispatch) remain fully active and unaffected.Verifying this change
This change is a CI configs adjustment and does not alter source code