{"push_id":722415564,"size":1,"distinct_size":1,"ref":"refs/heads/ct-dotenv","head":"37edd8de16360c1d6de85fb8f4e3ab979adb3d23","before":"d49031282c8333af164668ee3b0d3398639fd0cf","commits":[{"sha":"37edd8de16360c1d6de85fb8f4e3ab979adb3d23","author":{"email":"711c73f64afdce07b7e38039a96d2224209e9a6c@thorn.co","name":"Chris Thorn"},"message":"Include .env in the repo\n\nMoves .sample.env to .env. This file has all the config necessary to get\nrunning in development and `cp .sample.env .env` was in `bin/setup`. If\nthis file just exists as `.env` in the repo, then the setup step is not\nneeded and things should Just Work™ out of the box. The dotenv [docs][1]\neven recommend doing this to ease new developers onto the project.\n\nAdditionally, our heavy use of `ENV.fetch` is now causing the test suite\nto [fail][2] on CircleCI, because the database is being setup before the\n`pre` hook fires. With `.env` the test suite will work fine without this\nsetup.\n\nLocal customizations can be added to `.env.local`, which is ignored.\n\n[1]: https://github.com/bkeepers/dotenv#should-i-commit-my-env-file\n[2]: https://circleci.com/gh/thoughtbot/hound/202","distinct":true,"url":"https://api.github.com/repos/thoughtbot/hound/commits/37edd8de16360c1d6de85fb8f4e3ab979adb3d23"}]}