Regarding merge conflicts, they are caused by unrelated changes introduced after this fix.
Please advise if you want me to resolve them, or if maintainers prefer handling it.

@michalnik I'm not a maintainer but I think you will need to resolve the conflicts before a reviewer looks at the pull request. After a successful review and the ticket is marked for checkin, then a merger will look at the pull request.

@michalnik I'm not a maintainer but I think you will need to resolve the conflicts before a reviewer looks at the pull request. After a successful review and the ticket is marked for checkin, then a merger will look at the pull request.

Ok, currently I will start working on it

@coolbootscoder Thanks for the note! I double-checked the Django docs and you're correct — conflicts need to be resolved before a reviewer can look at the PR:
https://docs.djangoproject.com/en/dev/internals/contributing/writing-code/working-with-git/#after-upstream-has-changed

Sorry, currently I am struggling with anything from my previous commits did not work as expected.

At my localhost, runtests ended up with success! 💯

I made changes in the core of the autodetector tool used while migrations run and It has potential to fix the bug.

So, I hope, that we can discuss what i am not sure what to do with it or anything you want.

I wrote 2 kinds of tests:

1. integration (regression tests) - module test_autodetector_unmanaged
2. unit tests after the change - module test_autodector (currently in the same commit as the first)

Questions:

1. I think that integration tests should be somewhere else but I dont know where ... ?
2. I think that unit tests cover the main problem, but maybe it is not cover all cases ... ?

Please, add the label "needs discussion" if it makes sense to you, thanx 👍

📊 Coverage Report for Changed Files

-------------
Diff Coverage
Diff: origin/main...HEAD, staged and unstaged changes
-------------
No lines with coverage information in this diff.
-------------

Note: Missing lines are warnings only. Some lines may not be covered by SQLite tests as they are database-specific.

For more information about code coverage on pull requests, see the contributing documentation.