From e90803a1bf65a5c37d29f213d60d4e7896f12460 Mon Sep 17 00:00:00 2001 From: Benoit Daloze Date: Sun, 21 Feb 2021 11:51:34 +0100 Subject: [PATCH] Clarify how to find out the correct BUNDLE_ env var name --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 5b41e3c..e5ae4e8 100644 --- a/README.md +++ b/README.md @@ -167,7 +167,7 @@ as shown in the [example](#matrix-of-gemfiles). When using `bundler-cache: true` you might notice there is no good place to run `bundle config ...` commands. These can be replaced by `BUNDLE_*` environment variables, which are also faster. They should be set the `env` at the job level as shown in the [example](#matrix-of-gemfiles). -See the [Bundler docs](https://bundler.io/man/bundle-config.1.html) or look at `.bundle/config` locally for the environment variable names, +To find the correct the environment variable name, see the [Bundler docs](https://bundler.io/man/bundle-config.1.html) or look at `.bundle/config` after running `bundle config --local KEY VALUE` locally. To perform caching, this action will use `bundle config --local path $PWD/vendor/bundle`. Therefore, the Bundler `path` should not be changed in your workflow for the cache to work (no `bundle config path`).