Point the build status badge at GitHub Actions - #1119
Merged
Merged
Conversation
sanjain-progress
approved these changes
Sep 3, 2026
The README's build badge still pointed at the chef-oss/chef-cookstyle-main-verify Buildkite pipeline. CI moved to GitHub Actions, so the badge reflected a pipeline that no longer gates this repo. Swap it for the unit workflow, filtered to main, which is the workflow that actually runs the test suite on every push to main. Verified the badge SVG and its target both return 200 and that the badge currently renders 'unit - passing'. Signed-off-by: Tim Smith <tsmith84@proton.me>
tas50
force-pushed
the
github_actions_build_badge
branch
from
September 8, 2026 18:22
10b9fbe to
5f598d9
Compare
Contributor
There was a problem hiding this comment.
🟢 Approval recommended
The change is a straightforward README badge update and the referenced unit.yml workflow exists and matches the intended main-branch filtering.
Pull request overview
Updates the repository’s README build status badge to reflect the current CI system (GitHub Actions) instead of the retired Buildkite pipeline, so readers see the status of the workflow that actually gates main.
Changes:
- Replaces the Buildkite badge with a GitHub Actions badge for the
unitworkflow. - Filters both the badge and link target to
mainbranch runs for more relevant status and navigation.
File summaries
| File | Description |
|---|---|
| README.md | Swaps the Buildkite build status badge for the GitHub Actions unit.yml workflow badge/link filtered to main. |
Review details
- Files reviewed: 1/1 changed files
- Comments generated: 0
- Review effort level: Lite
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
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
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.
The README build badge still pointed at the
chef-oss/chef-cookstyle-main-verifyBuildkite pipeline. CI runs on GitHub Actions now, so the badge showed the status of a pipeline that no longer gates this repo.This swaps it for the
unitworkflow badge, filtered tomain— that is the workflow that actually runs the test suite on every push tomain. The link target uses?query=branch%3Amainso clicking through lands on the main-branch runs rather than all runs.Verification
unit - passing.bundle exec rake— 1239 examples, 0 failures; lint andvalidate_configpass.Left alone deliberately: there is also a
lintworkflow running onmainthat has no badge. Adding one is outside what this change is for, so flagging it rather than bundling it in.