ci: add scheduled 8-hour status check via reusable workflow#14
Merged
miguemagicdev merged 3 commits intomainfrom Feb 22, 2026
Merged
ci: add scheduled 8-hour status check via reusable workflow#14miguemagicdev merged 3 commits intomainfrom
miguemagicdev merged 3 commits intomainfrom
Conversation
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
1 participant
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
This PR introduces a scheduled health check to ensure repository stability even when no code changes are being pushed. It implements a reusable workflow pattern to keep our CI logic centralized.
Changes
status-checks.yml: Added the workflow_call trigger. This allows the workflow to be executed by other workflows (acting as a "reusable" workflow) without duplicating the job logic.scheduled-checks.yml: Created a new workflow that triggers every 8 hours (at 0, 8, and 16 UTC) using a cron schedule. It calls the existing status check jobs.Why this approach?
Instead of copying the test logic into a new file, we are now using workflow_call. This ensures that any future updates to our test suite only need to be made in one place (
status-checks.yml), while still allowing the scheduled trigger to run the exact same suite.