title: Should Django migrations live in source control?
body: <p>As the title says... I'm not sure if <a href="https://docs.djangoproject.com/en/1.8/topics/migrations/">Django migrations</a> should live in source control. </p>
  
  <p>For:</p>
  
  <ul>
  <li>If they get accidentally deleted from my local machine, it's going to cause me issues next time I want to run a migration... right? So it would be useful for me to have them. </li>
  </ul>
  
  <p>Against:</p>
  
  <ul>
  <li>Devs setting up the project for the first time shouldn't need to run them, they can just work straight from the models file. </li>
  <li>They seem like machine-specific cruft. </li>
  <li>Could they potentially reveal things I don't want about the database?</li>
  </ul>