title: Laravel migration works in strange way
body: <p>I've dropped my test database then I want to create new database using saved migrations:</p>
  
  <pre><code>2017_03_01_000000_create_api_table.php
  2017_03_06_000000_create_beeline_calls.php
  2017_03_13_000000_modify_beeline_emails.php
  2017_03_14_000000_interactive_forms.php
  2017_03_16_000000_model_instances.php
  2017_03_24_000000_create_objects.php
  2017_03_24_000001_create_objects_tables_v2.php
  2017_03_24_000003_make_comments_without_users.php
  2017_03_27_000000_add_processed_to_announcements.php
  2017_03_29_000000_create_ads_channels.php
  2017_03_29_000001_announcement_client.php
  2017_04_06_000000_create_filters.php
  2017_04_07_000000_create_new_input_types.php
  </code></pre>
  
  <p>When I run <code>php artisan migrate --pretend</code></p>
  
  <pre><code>  [Doctrine\DBAL\Schema\SchemaException]                                                                  
    There is no column with name 'creator_id' on table 'application_model_instance_announcement_comments'.
  </code></pre>
  
  <p>But first migration file to run is <code>2017_03_01_000000_create_api_table.php</code></p>
  
  <p>Why does it run not from start? Database is empty, <code>migrations</code> table is empty.
  As I understand Laravel should run migration files in alphabetical order.</p>