0

I think everybody had that problem. When you colleague creates a migration and you forget to run it after git pull. As I understand, this can be done by post-checkout git hook. Is there a ready solution?

If not, suggest how to make this check. Simple solution is to run rake db:abort_if_pending_migrations in git hook, but it will be too slow.

icem
  • 707
  • 7
  • 12

2 Answers2

4

I've done a gist with ruby code that does that check. It's useful to execute it at post-merge and post-checkout hooks.

The main idea is to diff current head with previous head state (HEAD@{1} , which is state before git pull) and search if there was any changes in db/migrate folder.

Thanks to Shadwell for finding almost working solution which I forked.

icem
  • 707
  • 7
  • 12
1

I found this post that has a ruby script and steps to follow to get it running. It looks like it will do what you want, and will optionally run the migrations too. It does it by checking for changes in the db/migrate folder. It does it as a post-merge hook.

Shadwell
  • 34,314
  • 14
  • 94
  • 99
  • Thanks for finding that gist! But unfortunately it doesn't support ruby 1.9 and actually don't detect migration if it was committed before previous commit. I'm going to fix it. – icem Aug 06 '13 at 10:27
  • Ah, okay, nice one. It got you a step in the right direction then, if not all the way :) – Shadwell Aug 06 '13 at 11:44