Scaffold for checking whether we should run db related tasks
We actually need to perform this check BEFORE pushing the code to heroku, not after
Implement a proper check for whether we should run db:seed and / or db:migrate
Its db/migrate, not db/migrations
We need to fetch the latest changes from heroku before attempting to check for migrations / seeds changes
Add wildcard to check if seeds need to be run

The reason why I am not checking for db/seeds.rb is that people might
have different seeds per environment by using https://github.com/james2m/seedbank
or some other way to structure the seeds.
We dont need to do this

If a push to heroku fails, it wont have the remote references updated
and the diff will still match
Merge pull request #33 from Helabs/fr-run-db-tasks-when-needed

Skip DB related tasks if nothing has changed since the last deploy