ci(prettier): show diff if prettier made changes

[Finkregh]

The normal output is not helpful, see also: prettier/prettier#6885

Changes

Linting with prettier now shows a diff if there are changes. This makes it easier to see what changes it actually want (not only the file names as before).

Context

https://github.com/renovatebot/renovate/actions/runs/10395128990/job/28798791562?pr=30680
Output here does not really help.

Documentation (please check one with an [x])

• I have updated the documentation, or
• No documentation update is required

How I've tested my work (please select one)

I have verified these changes via:

• Code inspection only, or
• Newly added/modified unit tests, or
• No unit tests but ran on a real repository, or
• Both unit tests + ran on a real repository

[secustor]

Is there a reason you can not simply run lint-fix or prettier-fix ?

[Finkregh]

Is there a reason you can not simply run lint-fix or prettier-fix ?

Does that show a diff? Or does it push changes back into PR? I'd be fine with either one :)

[secustor]

This is run locally to fix such issues automatically and should be then commited by the dev.
See this section of the local development guide: https://github.com/renovatebot/renovate/blob/main/docs/development/local-development.md#linting-and-formatting

[Finkregh]

It would still be nice if the CI would show me what should be changed, not everyone is ~willing/~able to setup that quite huge development environment :)

What do you think about adding a link to the dev-docs if prettier fails? @secustor

[rarkins]

@Finkregh what's the problem you're trying to solve?

e.g you submit a PR which has prettier problems, and it fails on CI, and you want more details?

I don't object to this, but the "next step" will still be to run pnpm prettier-fix. Instead do you plan to fix prettier problems by hand using the diff?

[Finkregh]

@rarkins yes, exactly. Make it at least an option to see what the files should look like :)

[rarkins]

Seems ok for me for those who want to contribute via the GitHub UI and not Codespaces or locally. @secustor wdyt?

[secustor]

Fine by me, though not sure if this will really be that helpful as Github UI messes with whitespace in the Actions UI as far as I know.

[renovate-release]

🎉 This issue has been resolved in version 38.41.0 🎉

The release is available on:

• GitHub release
• npm package (@latest dist-tag)
• 38.41.0

Your semantic-release bot 📦🚀