Open giedriusr opened 1 month ago
The truth is, I only half-understand how Actions works and like any CI specification, the feedback loops are too slow and the use cases are too diffuse to really get my arms around them for very long, even when I do.
For your specific case, I think you should be able to just remove the ruby/setup-ruby@v1 step, since 1.0 and later of this action includes it.
More generally, it would seem that an this action could define inputs as parameters users could set, and then one such input (say, rubyVersion
) which would be the default for what we tell ruby/setup.
Hello,
Upgrading the gem from 0.0.5 => 1.0.0 broke our flow. After investigating your
action.yml
file I see that it points to "ruby" which probably uses the newest ruby version out there: https://github.com/standardrb/standard-ruby-action/blob/main/action.yml#L16In our case, we have
.ruby-version
file, where we defined3.2.2
and also insige Gemfile. Ruby Linter flow doesn't take into consideration. Ruby version mismatch causes the failure of Github Actions.Our action.yml
Is it a bug or something has to change with our Action file?
Thank you