[now-static-build] Add test for BUNDLE_WITHOUT env var
#3070
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
leo
approved these changes
Sep 24, 2019
|
This is incredible! I'm so glad they already consume the env var on their own. |
styfle
added a commit
that referenced
this pull request
Sep 30, 2019
This adds a test which confirms that `BUNDLE_WITHOUT="test:development"` works properly. This env var is equivalent to `bundle install --without test development`. There's no code change here because groups are defined by the user, therefore they must define which ones to ignore (if any). - Groups Guide: https://bundler.io/v2.0/guides/groups.html - BUNDLER_WITHOUT: https://bundler.io/v2.0/bundle_config.html#LIST-OF-AVAILABLE-KEYS - Example Gemfile: https://github.com/thoughtbot/administrate/blob/master/Gemfile PRODUCT-133 #close
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds a test which confirms that
BUNDLE_WITHOUT="test:development"works properly.This env var is equivalent to
bundle install --without test development.There's no code change here because groups are defined by the user, therefore they must define which ones to ignore (if any).
PRODUCT-133 #close