Closed jaredcwhite closed 2 years ago
Perhaps including detection of ruby management via asdf as to generate a .tool-versions instead?
While asdf can read .ruby-version given the legacy_version_file = yes
configuration, this would make the process entirely seamless for the user.
Thanks for mentioning that @manuelgomes. One of the reasons though it's actually important to include .ruby-version
is to ensure hosting services and other users—whether using RVM, rbenv, asdf, or something else—will switch to the correct Ruby version. .tool-versions
would only benefit the asdf user. Maybe we can just document the legacy_version_file = yes
tip in our installation instructions/default readme template.
When a new project is created, add the current Ruby version to a new
.ruby-version
file.