docs: fix example status badge in contributing#1412
Merged
jennifer-shehane merged 1 commit intocypress-io:masterfrom Mar 24, 2025
Merged
docs: fix example status badge in contributing#1412jennifer-shehane merged 1 commit intocypress-io:masterfrom
jennifer-shehane merged 1 commit intocypress-io:masterfrom
Conversation
|
This comment was marked as outdated.
This comment was marked as outdated.
jennifer-shehane
approved these changes
Mar 24, 2025
|
🎉 This PR is included in version 6.8.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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
3 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.
Issue
The example badge in the CONTRIBUTING > Adding a new example section shows "no status" instead of the expected "passed" status.
Changes
Update the syntax of the
example-chromebadge in the CONTRIBUTING > Adding a new example section to use the current format as already corrected in the README > Chrome section.