Add SemVer compatibility badge to README #1289
Merged
Conversation
This file contains 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
vbrazo
force-pushed
the
master
branch
3 times, most recently
from
69291b2
to
5cc660c
Compare
vbrazo
force-pushed
the
master
branch
3 times, most recently
from
a2a9f17
to
4384168
Compare
vbrazo
approved these changes
Oct 20, 2019
sanikkenway
added a commit
to sanikkenway/faker
that referenced
this pull request
Oct 22, 2019
Add SemVer compatibility badge to README (faker-ruby#1289)
michebble
pushed a commit
to michebble/faker
that referenced
this pull request
Feb 16, 2020
davidmorton0
pushed a commit
to davidmorton0/faker
that referenced
this pull request
Jul 12, 2021
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.
Would you be up for adding a badge that shows how SemVer compliant / bug free new releases of faker are? I was looking through the data we gather at Dependabot and realised we could put one together, so I threw together the below:
If you click through then there's a description of how it's calculated - basically it takes all of the relevant updates Dependabot has done for projects that use faker and checks what percentage of the time specs pass on the upgrade PR.
(The missing 2% in the badge is probably from people with flaky tests. I'm working on removing them from the dataset.)