When doing a makemigration --dry-run skip asking about default values for non-nullable fields?

[shige.abe@…]

Given that the output for --dry-run is just a summary of what's changing, I wouldn't expect to need to supply default values for new non-nullable fields.

[mardini]

I agree with you. No need for that step since the default value won't be used anyway.
I'll leave the ticket to a core developer to accept though.
Here's my PR: ​https://github.com/django/django/pull/2698
Thanks.

[Tim Graham <timograham@…>]

In 63fc91b3cac523690655c1d86d09972e0cc3a29d:

Fixed #22676 -- makemigrations --dry-run should not ask for defaults

Made the fix in InteractiveMigrationQuestioner class code, rather than
MigrationAutodetector, because --dry-run shouldn't affect whether
MigrationAutodetector will detect non-nullable fields, but the
questioner should skip the question and returns a None for default
(since that won't be used anyway) if --dry-run is used.

[Tim Graham <timograham@…>]

In a59870e21784166725f7cb3230becef50553ee3a:

[1.7.x] Fixed #22676 -- makemigrations --dry-run should not ask for defaults

Made the fix in InteractiveMigrationQuestioner class code, rather than
MigrationAutodetector, because --dry-run shouldn't affect whether
MigrationAutodetector will detect non-nullable fields, but the
questioner should skip the question and returns a None for default
(since that won't be used anyway) if --dry-run is used.

Backport of ee14961a2a from master