setup-ruby icon indicating copy to clipboard operation
setup-ruby copied to clipboard

An action to download a prebuilt Ruby and add it to the PATH in 5 seconds

Results 36 setup-ruby issues
Sort by recently updated
recently updated
newest added

I thought a note about the 'available Ruby version' issue would be helpful at the top of the document. It does overlap with the [VERSIONING paragraph](https://github.com/ruby/setup-ruby/blob/699560a00d6008d3844c932e3e15c404aaad9508/README.md#versioning)...

using: self-hosted macOS (M1 chip) ``` - name: Install ruby uses: ruby/setup-ruby@v1 env: ImageOS: macos1015 ``` ### 1st `libgmp.10.dylib` error: The installation failed on "Print Ruby version" step with the...

Using the caching functionality of the action various times using different working-directories leads to incorrectly restored caches. First workflow runs and caches `website/vendor/bundle` ```yml - uses: ruby/setup-ruby@v1 with: bundler-cache: true...

On the Git LFS project we have an older Windows CI [workflow](https://github.com/git-lfs/git-lfs/blob/5e126183dd2b9fcb66f42429ed41175e7544fde0/.github/workflows/ci.yml) which uses the legacy `actions/setup-ruby@v1` action, and which we might like to upgrade to `ruby/setup-ruby@v1` as it would...

Hi, I wanted to save and restore to a file outside of `vendor`. I wanted to use Brakeman to scan my app, and include some code from one of my...

## Motivation Currently, if one is using this action to set up Ruby and manage caching of their gemset, there is no way to *micro-manage * the environment before Bundler...

It's possible to add or skip certain gem groups with `with:` and `without:` config options (via corresponding `BUNDLE_WITH` and `BUNDLE_WITHOUT` env variables) which might set an incomplete cache. It's because...

Hello Team, Our use case is to use this action on multiple self hosted runners running on single host. Runners are running in different directory and trying to access cache...

Many users who wants use `3.0.x` write `ruby-version: 3.0` by mistake. `3.0` interpreted as `3` on GitHub Actions. For example, following workflow step prints `3` only. ```yaml env: env_var: 3.0...

It would be helpful to add support for a `token` parameter so that we can more easily avoid GitHub rate limits. https://github.com/ruby/setup-ruby/blob/master/ruby-builder.js#L91