Use --skip-empty for coverage report

[marcelofern]

This is a better alternative to not running coverage against init.py files entirely. This could've been a problem if those files had code in it.

[github-actions]

Coverage Report Results

Name	Stmts	Miss	Branch	BrPart	Cover
src/django_pg_migration_tools/management/commands/migrate_with_timeouts.py	25	0	10	0	100%
src/django_pg_migration_tools/operations.py	67	0	6	0	100%
src/django_pg_migration_tools/timeouts.py	73	5	36	2	92%
TOTAL	165	5	52	2	96%

3 empty files skipped.

[DHUKK]

🚀

[meshy]

Have you considered --skip-covered instead, so that this shows only files which need work?

[marcelofern]

Have you considered --skip-covered instead, so that this shows only files which need work?

Thanks for the suggestion, I will have a look with more detail.
The output looks like this:

coverage report --skip-covered --skip-empty --format= --data-file=build/coverage

Name                                        Stmts   Miss Branch BrPart  Cover
-----------------------------------------------------------------------------
src/django_pg_migration_tools/timeouts.py      73      5     36      2    92%
-----------------------------------------------------------------------------
TOTAL                                         165      5     52      2    96%

5 files skipped due to complete coverage.

EDIT: This looks a good addition for when we get to 100% coverage. So the bot can be conditional to only posting on PRs that decrease coverage.