good_migrations 0.0.1 → 0.0.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 300eaa36799b25cbfd31a71d5402f341b0ce5092
-  data.tar.gz: 120d0e6a21210da185e386ab9a3413e59fa36048
+  metadata.gz: 05eb20b7481ddae6720347b0c84275997ff53e72
+  data.tar.gz: b7c85f764f8f2c22a3988517f2c272cdb59d0016
 SHA512:
-  metadata.gz: 973fd6176fb703e45a5fa1ebcd33691a7ab2ca03d89a3f7764472f91928aebfd49b9535a4a8519f9620150d9dc868cd7283d916f2c9a85f3be2959a8c6bff7ab
-  data.tar.gz: 1590102bea210bd1f4edaf8f1dfd6c1d94cad99720c4da13d89f6416191857a1e830059bfdbb01ed76aaf8e6b33217bef22b08fa27f72206b0213c8423236872
+  metadata.gz: b79f08edebb75e97c2358064c31d8c5d2de7e4cb483b5e4f7e61a4fe04b6550156c271995249af7327a66b1f5767269830ec0fe01b7144a4fcaa6a257d244689
+  data.tar.gz: 285bfb5be43c16860c0e6bff42c5e024d24199d4a9a84e9de1f946d04a979bbac87156c0603124c87aac80aecef81f0cd47690daf699bf27c73f2770ad0465fc

data/.travis.yml

@@ -2,6 +2,8 @@ language: ruby
 sudo: false
 rvm:
   - 2.2.3
+before_script:
+  - cd example && bundle install
 env:
   - RAILS_ENV=3.1.0
   - RAILS_ENV=4.0.0

data/README.md

@@ -1,7 +1,10 @@
 # good_migrations
 
-**tl;dr: prevent loading app code from migrations by adding `good_migrations` to
-your Gemfile**
+[![Build Status](https://travis-ci.org/testdouble/good-migrations.svg?branch=master)](https://travis-ci.org/testdouble/good-migrations)
+
+This gem prevents Rails from auto-loading app code while it's running migrations,
+preventing the common mistake of referencing ActiveRecord models from migration
+code.
 
 ## Usage
 
@@ -30,12 +33,12 @@ That means that if your migrations reference the ActiveRecord model objects
 you've defined in `app/models`, your old migrations are likely to break. That's
 not good.
 
-By adding this gem to your project's `Gemfile`, autoloading paths inside 'app/`
+By adding this gem to your project's `Gemfile`, autoloading paths inside `'app/'`
 while running any of the `db:migrate` Rake tasks will raise an error, explaining
 the dangers inherent.
 
 Some will reply, "who cares if old migrations are broken? I can still run `rake
-db:setup` because I have a `db/schema.rb file". The problem with this approach
+db:setup` because I have a `db/schema.rb` file". The problem with this approach
 is that, so long as some migrations aren't runnable, the `db/schema.rb` can't
 be regenerated from scratch and its veracity can no longer be trusted. In
 practice, we've seen numerous projects accumulate cruft in `db/schema.rb` as the
@@ -43,6 +46,9 @@ result of erroneous commits to work-in-progress migrations, leading to the
 development and test databases falling out of sync with production. That's not
 good!
 
+For more background, see the last section of this blog post on [healthy migration
+habits](http://blog.testdouble.com/posts/2014-11-04-healthy-migration-habits.html)
+
 ## Options
 
 There's no public API to this gem. If you want to work around its behavior, you

data/good_migrations.gemspec

@@ -19,6 +19,7 @@ Gem::Specification.new do |spec|
   spec.require_paths = ["lib"]
 
   spec.add_dependency "railties", ">= 3.1"
+  spec.add_dependency "activerecord", ">= 3.1"
 
   spec.add_development_dependency "bundler", "~> 1.10"
   spec.add_development_dependency "rake", "~> 10.0"

data/lib/good_migrations/version.rb

@@ -1,3 +1,3 @@
 module GoodMigrations
-  VERSION = "0.0.1"
+  VERSION = "0.0.2"
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: good_migrations
 version: !ruby/object:Gem::Version
-  version: 0.0.1
+  version: 0.0.2
 platform: ruby
 authors:
 - Justin Searls
@@ -25,6 +25,20 @@ dependencies:
     - - ">="
       - !ruby/object:Gem::Version
         version: '3.1'
+- !ruby/object:Gem::Dependency
+  name: activerecord
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '3.1'
+  type: :runtime
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '3.1'
 - !ruby/object:Gem::Dependency
   name: bundler
   requirement: !ruby/object:Gem::Requirement