Soften checks for Ruby head in CI #286
Comments
This was referenced Jan 30, 2024
saulecabrera
added a commit
that referenced
this issue
Feb 8, 2024
Ruby head is still failing on pull requests so I'm opting to disable it until we decide what to do with it in #286.
saulecabrera
added a commit
that referenced
this issue
Feb 8, 2024
Ruby head is still failing on pull requests so I'm opting to disable it until we decide what to do with it in #286.
saulecabrera
added a commit
that referenced
this issue
Feb 9, 2024
Ruby head is still failing on pull requests so I'm opting to disable it until we decide what to do with it in #286.
saulecabrera
added a commit
that referenced
this issue
Feb 9, 2024
Ruby head is still failing on pull requests so I'm opting to disable it until we decide what to do with it in #286.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There have been several instances (the most recent one) where Ruby's head version fails in CI. This is not always ideal, given that most of the time the failures are not directly related to changes in a particular pull-request, instead the failures are related to changes in Ruby's latest version. If there's interest in keeping checks against Ruby's head version, would it be reasonable to "soften" these checks and emit a warning instead of an error?
The text was updated successfully, but these errors were encountered: