docs: update build status badge to track scheduled-checks#17
Merged
miguemagicdev merged 1 commit intomainfrom Feb 22, 2026
Merged
docs: update build status badge to track scheduled-checks#17miguemagicdev merged 1 commit intomainfrom
miguemagicdev merged 1 commit intomainfrom
Conversation
This change ensures the repository health status is accurately reflected in the README by pointing the badge to the 'scheduled-checks' workflow rather than 'status-checks'. The previous workflow was intermittently returning a "no status" message. By switching to the scheduled variant, the badge now detects the state of the repo based on regular automated intervals, providing better visibility into the project's ongoing health.
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.
Why is this change being made?
The existing README badge was frequently displaying a "no status" message. This occurred because the
status-checks.ymlworkflow was not providing a consistent heartbeat for the repository's health.Detailed Description of the Change:
scheduled-checks.ymlinstead ofstatus-checks.yml.flat-squarestyle andgithubactionsbranding for visual continuity.Technical Details