First, these two elements have no direct relationship to each other. Emptying the migrations table does not at all affect your need (or non-need) to run makemigrations.
The migrations table is not written by makemigrations, it is written by the migrate command.
This is, in general, a bad idea unless you know what to do from this point. (You would need to run your migrations one by one, using the --fake parameter to re-mark a migration as having been run without actually trying to perform the sql updates.)
Ignoring everything you’ve done before now - it looks like you have a database with migrations that have successfully run.
Is there a current issue needing to be addressed?
Note for future reference: Do not delete anything related to migrations without ensuring you understand why you are doing it, and how it affects the migrations environment. Do not delete migration files. Do not empty the migrations table. Otherwise, you are likely going to put yourself in a position where your easiest solution is to delete the database and reinitialize it.