chore(docs): fix CI badge status display#1294
Merged
styfle merged 2 commits intovercel:mainfrom Oct 27, 2025
Merged
Conversation
This comment was marked as outdated.
This comment was marked as outdated.
styfle
reviewed
Oct 27, 2025
styfle
changed the title
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.
Situation
The CI badge is showing an incorrect failing status.
The badge for the CI workflow .github/workflows/ci.yml, displayed in the readme.md, shows "CI failing", although the action last ran successfully in the default
mainbranch.The badge is using the URL:
https://github.com/vercel/ncc/workflows/CI/badge.svg
The syntax of this URL is not in line with the GitHub documentation Adding a workflow status badge which specifies the format:
Change
In the readme.md change the URL to
Verification
Check the readme.md and confirm that the badge status conforms to the status of the latest action run in the default
mainbranch.Currently this should be showing