thoughtbot--factory_bot/gemfiles
Daniel Colson c8b1a2c907
Run travis against Rails master (#1388)
This will allow us to address any deprecations and incompatibilities
before new versions of Rails are released, making it easier for folks to
upgrade their applications.

I am ignoring the gemfile.lock here because I want CI to always run
against the latest master, not a specific commit.

I am allowing failures on Travis because I don't want these failures to
block people's PRs (like what we do with ruby-head).
2020-04-29 19:09:11 -04:00
..
4.2.gemfile Get default strategy registration working on JRuby 2019-10-02 18:56:58 -04:00
4.2.gemfile.lock Bump version to 5.2.0 2020-04-24 11:57:03 -04:00
5.0.gemfile Get default strategy registration working on JRuby 2019-10-02 18:56:58 -04:00
5.0.gemfile.lock Bump version to 5.2.0 2020-04-24 11:57:03 -04:00
5.1.gemfile Get default strategy registration working on JRuby 2019-10-02 18:56:58 -04:00
5.1.gemfile.lock Bump version to 5.2.0 2020-04-24 11:57:03 -04:00
5.2.gemfile Get default strategy registration working on JRuby 2019-10-02 18:56:58 -04:00
5.2.gemfile.lock Bump version to 5.2.0 2020-04-24 11:57:03 -04:00
6.0.gemfile Get default strategy registration working on JRuby 2019-10-02 18:56:58 -04:00
6.0.gemfile.lock Bump version to 5.2.0 2020-04-24 11:57:03 -04:00
master.gemfile Run travis against Rails master (#1388) 2020-04-29 19:09:11 -04:00