Add specs for CapistranoExtensions#trigger_update?
Remove unnecessary stub from specs
Handle edge case where a new migration does not change the schema

This can occur when a migrations makes changes to data rather than
table structure and is run after another migration has been added
with a later creation time.
fixup! Handle edge case where a new migration does not change the schema

There is no need to check for changes to the schema if we are checking
changes to the migrations directory
Merge pull request #76 from mocoso/handle-no-schema-change-migrations

Handle edge case where a new migration does not change the schema