title: Laravel migration in different branches
body: <p>In my app, built with Laravel 5.1, I have a branch dev.</p>
  
  <p>I had to implement 2 new features, so I created first branch (starting from dev) that needed 2 tables (so new migrations), then, when I finished it, I created second branch (starting to dev) and also this feature needed a different table so new migration.</p>
  
  <p>So my situation is something like:</p>
  
  <pre><code>branch 1 -&gt; migration1
  branch 2 -&gt; migration2, migration3
  </code></pre>
  
  <p>But now I need to change (many columns) the table related to branch1 so I should rollback migration, because I would not make new migration for change but I would rollback migration and recreate.</p>
  
  <p>But my problem now is that if I return in my branch1 and try to do:</p>
  
  <pre><code>php artisan:migrate rollback
  </code></pre>
  
  <p>The latest migrations (on my db) are the tables for branch2 (migration2, migration3) and not the table related to branch1 (migration1).</p>
  
  <p>So what is the right way for manage migration between many branch?</p>