Database Manager: using git to revert a change results in a corruption in the migration directory

There was no change to revert because of the error encountered in Database Manager: changing the name of a table breaks the database manager

Once again, the manager didn’t create a change file – rightly so – but it continues to show that changes need to be applied.
image

I had a previous git commit, so I tried to revert, but somehow the Database Manager has a different way of storing changes and now it’s looking for a migration file that doesn’t exist.