Benoit Daloze

@artygus Are you still interested to make a PR for this?

Duplicate of https://github.com/ruby/setup-ruby/issues/136#issuecomment-753613782, see reasoning there. What's the issue to use the standard Bundler path, which is `vendor/bundle`? It sounds an issue of Brakeman which should have a way to...

I think it would be OK to use the value of BUNDLE_PATH if set to a relative path. It should be an error if it's an absolute path though, as...

@januszm That seems completely unrelated, please file a separate issue if still a problem. Gems are never shared between Ruby versions with `bundler-cache: true`, so it sounds like you're missing...

People should already be aware of this via the issue template (https://raw.githubusercontent.com/ruby/setup-ruby/master/.github/ISSUE_TEMPLATE/bug_report.md). I think this will not help more, people who don't know how to read the template when filing...

Maybe we should use an Issue Form template like https://github.com/Homebrew/brew/blob/master/.github/ISSUE_TEMPLATE/bug.yml

> Having the info right at the top so one doesn't even need to scroll both here and in the [Marketplace](https://github.com/marketplace/actions/setup-ruby-jruby-and-truffleruby) will possibly mean people don't need to see the...

Short answer: this action and the the built Rubies do not support any other architecture than x86_64. We should probably update it to error early in that case. It might...

> any plan to support M1 in the near future ? We'd need M1 GitHub-hosted runners for that, so I can build the releases. Until then, no, but it might...

@rgaufman This needs better docs, but this should already work if you build your own ruby in the hosted tool cache and create the "complete" file: https://github.com/ruby/setup-ruby/blob/6148f408d35df04b0189be5e64c1458377b8ae13/common.js#L165-L186 That's the overall...