If a whole of people thought that running code through a linter or formatter was objectionable, I'd probably just dismiss their beliefs as invalid rather than adding the linter or formatter as a co-author to every commit.

▲

jacquesm 3 hours ago | parent | next [-]

A linter or a formatter does not open you up to compliance and copyright issues.

▲

mikkupikku 4 hours ago | parent | prev | next [-]

Like frying a veggie burger in bacon grease. Just because somebody's beliefs are dumb doesn't mean we should be deliberately tricking them. If they want to opt out of your code, let them.

▲

sysguest 3 hours ago | parent [-]

> frying a veggie burger in bacon grease

hmm gotta try that

▲

jitl 2 hours ago | parent [-]

I love black bean burgers (bongo burger near Berkeley is my classic), sounds like an interesting twist

	▲	jasomill an hour ago \| parent [-]
		Never fried one in bacon grease, but they are good with bacon and cheese. I have had more than one restaurant point out that their bacon wasn't vegetarian when ordering, though.

▲

runarberg 3 hours ago | parent | prev [-]

Linters and formatters are different tools then LLMs. There is a general understanding that linters and formatters don’t alter the behavior of your program. And even still most projects require a particular linter and a formatter to pass before a PR is accepted, and will flag a PR as part of the CI pipeline if a particular linter or a particular formatter fails on the code you wrote. This particular linter and formatter is very likely to be mentioned somewhere in the configuration or at least in the README of the project.