No commit activity in last 3 years
No release in over 3 years
Check and fail if args include migration and app code changes.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
 Dependencies

Development

~> 1.16
~> 5.0
~> 10.0
 Project Readme

MigrationsWatchdog

This tool helps you check if the passed paths include migration and app code changes.

Installation

Add this line to your application's Gemfile:

gem 'migrations_watchdog'

And then execute:

$ bundle

Or install it yourself as:

$ gem install migrations_watchdog

Usage

You can call the CLI passing the paths to check:

$ migrations_watchdog app/models/foo.rb db/structure.sql
Migrations and app code detected. Move out the following files:
app/models/foo.rb

At Envoy we use this tool in our CI flow to force separation between migration and app code changes in each pull request.

Our CircleCI configuration has a task like the following:

- run:
    name: Migrations and app code check
    type: shell
    command: git --no-pager diff --name-only HEAD $(git merge-base HEAD master) | xargs migrations_watchdog

Development

After checking out the repo, run bin/setup to install dependencies. Then, run rake test to run the tests. You can also run bin/console for an interactive prompt that will allow you to experiment.

To install this gem onto your local machine, run bundle exec rake install. To release a new version, update the version number in version.rb, and then run bundle exec rake release, which will create a git tag for the version, push git commits and tags, and push the .gem file to rubygems.org.

Contributing

Bug reports and pull requests are welcome on GitHub at https://github.com/envoy/migrations_watchdog. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the Contributor Covenant code of conduct.

License

The gem is available as open source under the terms of the MIT License.

Code of Conduct

Everyone interacting in the MigrationsWatchdog project’s codebases, issue trackers, chat rooms and mailing lists is expected to follow the code of conduct.