Set RBENV_ROOT #81
Merged
Set RBENV_ROOT #81
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
added 2 commits
July 29, 2020 16:57
RBENV_HOME does not exist and won't be used by rbenv. Github action changes the HOME env variable so rbenv plugins are not available anymore. Using RBENV_ROOT tells rbenv where its config files are
vincentbrison
approved these changes
Jul 30, 2020
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.
fix #80
In the Dockerfile,
RBENV_HOMEwas set instead ofRBENV_ROOT. By default, rbenv uses "$HOME/.rbenv".Github Actions changes $HOME thus rbenv wasn't able to access our setup.
A test was added to ensure the fix works.