It seems most, if not all, operations inside hasura console generate migrations even if the operation fails. Examples:

• Inserting data with invalid query and ticking migration box
• Attempting to set a table as enum without rows
• Modifying an action with invalid action definition

All of these actions fail to succeed on hasura console, but the console still creates migration files for them.
This problem keep migrations inconsistent with DB state, and very often leads to failure when applying migrations on another computer.

Is this the intended behaviour or is it a bug? I believe a more correct approach would be only to generate migrations for operations that succeed.