Migrations ignored from git_commit_id when the app label does not exactly match the folder name

[phillipuniverse]

Here's a screenshot from the Pycharm debugger that shows the issue

The migration linter is checking for a migration with a tuple ("netsuite", "0012_added_netsuite_suiteapp_config") against the Django disk_migrations (self.migration_loader is the Django MigrationLoader).

This migration linter assumes that "netsuite" is a valid app name for Django. But it's not - Django doesn't know about an app called netsuite, it knows about one called integrations_netsuite. This is because we renamed it in a custom AppConfig in apps.py:

 class NetsuiteConfig(AppConfig): 
     name = "integrations.netsuite" 
     label = name.replace(".", "_") 

So the root issue is that the linter doesn't look truly at app labels, it only looks at folder structures.

This appears to only be an issue when used in concert with the git commit id.

Fix for this issue is at #248 which takes the folder structure and converts it to the real Django app without assumptions about naming.

[David-Wobrock]

Hi @phillipuniverse

Thanks for the report! That's indeed something the linter should support.
I'll try to look into it and review #248 soon :)

[mjvankampen]

Ran into this as well!