Migration: git deployment with ENUM table causes metadata inconsistency

After git deployment or the migration using Hasura CLI of projects with ENUM table causes the metadata to be inconsistent.

It is because ENUM tables cannot be empty.
But when I click on the ENUM table, I am sent to the error screen.
And upon refresh redirected to the metadata inconsistency page.

I resolved the problem by adding the ENUM table entries by executing Raw SQL queries.
But I believe the Hasura UI could be improved to allow data insertion.

Start by reproducing a git deployment or Hasura CLI migration for a project with an empty ENUM table, then follow the UI path from clicking the table to the error screen and metadata inconsistency page. Done means the UI allows ENUM table entries to be inserted and the deployment or migration no longer leaves metadata inconsistent.

Written by the indexing model from the issue text.