You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are trying to decide on which rules should be the primary or canonical rules.
These current rules depend on a very old version of Bazel, fail on CI, but they have been designed with a typical Ruby/rails flow in mind. That's why we have rspec rules and rails example.
The alternative rules by Alex Radionov are much more modern, pass CI across multiple Ruby implementations, provide hermetic build of Ruby, but might be impractical for a large rails application.
I am looking for users of any Ruby rules to play with both and provide some feedback. If Alex's rules become the default, is there anything in this repo that we might want to carry over?
The text was updated successfully, but these errors were encountered:
kigster
changed the title
ATTENTION: real world ruby/bazel testers are needed
ATTENTION: YOUR OPINION MATTWRS! real world ruby/bazel testers are needed
Nov 28, 2023
kigster
changed the title
ATTENTION: YOUR OPINION MATTWRS! real world ruby/bazel testers are needed
ATTENTION: YOUR OPINION MATTERS S! real world ruby/bazel testers are needed
Nov 28, 2023
We are trying to decide on which rules should be the primary or canonical rules.
These current rules depend on a very old version of Bazel, fail on CI, but they have been designed with a typical Ruby/rails flow in mind. That's why we have
rspec
rules and rails example.The alternative rules by Alex Radionov are much more modern, pass CI across multiple Ruby implementations, provide hermetic build of Ruby, but might be impractical for a large rails application.
I am looking for users of any Ruby rules to play with both and provide some feedback. If Alex's rules become the default, is there anything in this repo that we might want to carry over?
The text was updated successfully, but these errors were encountered: