Fix bug with gem_excludes not being used on bundler gems #468
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 is an upstream commit authored by @stalbot.
Unclear why in the original code
exclude_gems
was set to false if any files were found in the Git gem. It caused the condition to check forconfig.gem_excludes
to not trigger.(Looks like gem_excludes will not work neither when spec.source is ::Bundler::Source::Path)
Co-authored-by: Steven Talbot steven@looker.com