currently django would raise exception if we tried to reverse the migrations because the data migration has no backwards. This avoids that problem read more
Coverage remained the same at 97.301% when pulling cb0754900cb9dea31a0152b31ee8ec94df36a839 on django-doctor:django-doctor-fix-1611125743317.0503 into f16492dd399ca308c30eb7175d8da8dd97c4c08e on macropin:master.
currently django would raise exception if we tried to reverse the migrations because the data migration has no backwards. This avoids that problem read more
I found this problem during auditing your codebase. Read the full report