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.
There are 3 commits on this PR to refactor the CI yaml files.
Fix wrong comments.
The comments for the 2 cases were actually opposite.
GitHub Actions: Set the default value to allow-failure.
There is a way to omit the
allow-failure
when the case passes setting the default value. The tip is inspired by the rspec-core's GitHub Actions yaml file.Migrate Ruby 2.0.0 case in Travis to GitHub Actions.
We have actually Ruby 2.0.0 case on CentOS 7 case. I know the system Ruby in CentOS 7 is 2.0.0 until the CentOS 7 will be end of life. The tip using
name_extra
also comes from the rspec-core's GitHub Actions yaml file.I thought we could remove the Ruby 2.0.0 case in Travis CI. In other words, we may still want to keep the Ruby 2.0.0 in Travis for some reasons.
What do you think?