ragel.yml - use 'bundle exec rake' instead of 'rake' #3269
Merged
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.
Description
Rake 13.1.0 has been released, and the ragel CI is failing in my fork.
BUNDLE_PATH
is set by setup/ruby usingbundle config --local path <path>
, so the gems installed by it are not accessible unlessbundle exec
is used. Hence, one should always usebundle exec
orrequire 'bundler/setup'
.Your checklist for this pull request
[ci skip]
to the title of the PR.#issue
" to the PR description or my commit messages.