Coverage remained the same at 100.0% when pulling c84400b9cfdd83948757107b160d7195d5e99042 on 633_update_to_rails5 into d4c2033d0c767f27d1d73606141e18b3f6b77527 on dev.
Coverage remained the same at 100.0% when pulling 74079189f51c4a71db53fcba6349c09b99a3f757 on 633_update_to_rails5 into d4c2033d0c767f27d1d73606141e18b3f6b77527 on dev.
Coverage remained the same at 100.0% when pulling 013dd210365d8c2a2c6dcf0cab32a6d708f01c29 on 633_update_to_rails5 into d4c2033d0c767f27d1d73606141e18b3f6b77527 on dev.
Coverage remained the same at 100.0% when pulling c07dc2784bbec5dceb2da8ab14ba45485629a4c9 on 633_update_to_rails5 into d4c2033d0c767f27d1d73606141e18b3f6b77527 on dev.
Coverage remained the same at 100.0% when pulling d8e2bf706f8d42f7fa34faa7a458597a4215c7fc on 633_update_to_rails5 into d4c2033d0c767f27d1d73606141e18b3f6b77527 on dev.
Coverage remained the same at 100.0% when pulling 3e32cef15a81307ff58e3b6768da42d135bdbdaf on 633_update_to_rails5 into 8b5a0d2958b992d384b432a7377c739e6957f892 on dev.
Whoops, I somehow never reviewed the changes you applied after my initial comments. I've done so now, and will merge this once Travis runs through :) Let's find out what else will break with Rails 5 😆
Coverage remained the same at 100.0% when pulling c84400b9cfdd83948757107b160d7195d5e99042 on 633_update_to_rails5 into d4c2033d0c767f27d1d73606141e18b3f6b77527 on dev.