kobotoolbox / kpi / 30480037256 / 4

82%

master: 76%

push

github

ci(darker): print the diff so formatting failures are self-explanatory DEV-1034 (#7341)

### 💭 Notes

Follow-up to #7316. That PR correctly made the `darker` job trust
darker's exit code, but the command uses `darker --check`, which signals
formatting/isort findings through the **exit code only** and prints
nothing. The result: a real formatting failure shows up as a blank red ❌
with no output (see the silent failures on #7299 and #7339).

This adds `--diff` so darker prints the exact reformatting/isort patch
it wants. `--diff` does not change the exit code, so #7316's
crash-vs-clean behavior is preserved — the job just now explains itself.

Verified locally with the exact CI command against a real failing range:
- findings → `exit 1` **and** the patch is printed to stdout
- clean → `exit 0`, no output
- YAML parses

Devs hitting a red darker can then see what to run (`format-python.sh
origin/main`) instead of guessing.

CI/internal only, no behavior change.

3845 of 12680 branches covered (30.32%)

17106 of 37590 relevant lines covered (45.51%)

0.46 hits per line