Create a check for initial migrations

Today I found a code like this:

class Migration(migrations.Migration):

    # initial = True
    dependencies = []

And this was an initial migration for an app.

This suprised me:

1. It works correctly
2. It does not produce any warnings
3. It is cryptic

What am I concerned about? I have an impression that all migrations with dependencies = [] must be initial, because otherwise they should be dependent on a previous migration. Am I correct?

So, I guess we can check this pretty easily in case initial really works this way.

[skarzi]

hello @denisSurkov 👋

I think it’s still relevant, however, we haven’t got time to work on this issue, so any help is really appreciated. To be honest, I haven’t checked how to implement this feature, but the general process could look like this:

1. Let’s add a new file with checks to this directory a) Maybe MigrationLoader.graph.root_nodes() can be used to implement initial = True check
2. Let’s add a new app config class MigrationClasses to this file so migration-related checks can be included separately

Of course, don’t forget about unit tests of all newly introduced code. Let’s ping me if you have any questions etc 😉

[denisSurkov]

Hi

Is there any activity here? Is it still relevant?

And if so, what do you expect from this feature?