Use a more canonical way to require files #3
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
Reason for Change ================= * When using the gem as a git remote in bundler (either with a branch or without) in William, all files were `require`d. * Now it’s up on rubygems.org, it does not require any of the files. Changes ======= * Use the prescribed way to require all files in the `/lib` directory. While this seems aggressive to me, I guess it's standard.
|
👍 |
alieander
added a commit
that referenced
this pull request
Feb 3, 2016
Use a more canonical way to require files
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.
Reason for Change
required.Changes
/libdirectory. While this seems aggressive to me, I guess it's standard.