[ok_dad]

A clanker isn’t a human it’s a tool. I don’t write “Coauthored by VSCode” when I use find and replace.

[cperciva]

I write "reported by gcc16 -pedantic" when I'm fixing a bug, because it's useful to flag "this is how they issue became visible" in case readers want to use the same tool on their code.

The fact that it's just a tool is irrelevant. You don't need to mention search and replace because everyone already knows that exists... mind you I have had commit messages which included sed commandlines, for ease of future reuse.

[awesome_dude]

I know this is a bit off tangent - but can you please convey that point to every damned dev/team that ends up with a freaking ".vscode" directory in their repo

[1718627440]

I use the GNU Autotools toolchain to generate VSCode folders. We are not the same!

(The first sentence isn't a joke.)

[bulbar]

I have done that in the past to provide zero-setup development environments for our internal python packages.

What's the problem with the approach?

[rrvsh]

Do you also have .DS_Store tracked? If not, you are obviously not who the commenter is referring to and missing the point

[sodapopcan]

They don't know what a global git ignore is and if you tell them they don't care.

[sheept]

Find and replace behaves the same in most IDEs, but for large changes, the specific LLM can affect the generated code for the same prompt

[ok_dad]

So does my brain, but no one complains. If I’ve read and understand all of the code it’s effectively the same thing. I’m washing the LLM output so it’s clean. My brain parses the LLMs code and deems it safe.