Prevent const reassignment of GEMS_PENDING_ROOT #3518
Merged
+4
−2
Conversation
This file contains hidden or 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
When launched through the vmdb application, GEM_PENDING_ROOT is already set. This setup is mainly for testing and bootstrapping things in gems/pending and will go away when they are gemified.
Fryguy
force-pushed
the
guard_const_assignment
branch
from
dc11fe1 to
366f009
Compare
|
Checked commit Fryguy@366f009 with rubocop 0.32.0 |
chessbyte
added a commit
that referenced
this pull request
Jul 18, 2015
Prevent const reassignment of GEMS_PENDING_ROOT
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.
When launched through the vmdb application, GEM_PENDING_ROOT is already
set. This setup is mainly for testing and bootstrapping things in
gems/pending and will go away when they are gemified.
@chessbyte Please review.