Django migrations best practice
you should create migration files locally, migrate locally and test it, and then commit the files to version control. django docs says: 

The reason that there are separate commands to make and apply
  migrations is because you’ll commit migrations to your version control
  system and ship them with your app; they not only make your
  development easier, they’re also useable by other developers and in
  production.

if multiple developers are working on the same project, they dont have to create the migrate files, they just do migrate and everything is paradise.
I'm using Django 1.7 with migrations, and I'm not sure about what is the best practice, I should add the migrations files to my repository, or this is a bad idea?