Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Use a more canonical way to require files #3

Merged
merged 1 commit into from Feb 3, 2016
Merged

Use a more canonical way to require files #3

merged 1 commit into from Feb 3, 2016

Commits on Feb 3, 2016

  1. Use a more canonical way to require files 

    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.
    @adarsh
    adarsh committed Feb 3, 2016
    Copy the full SHA
    46d8f43 View commit details
    Browse the repository at this point in the history