This works now but could at some point fail with a shell error: argument list too long. Using xargs is one option and maybe markdown-lint has some other built-in function.

If a file has spaces that would also be problematic.

Same as before, you could just add xargs in front of pnpm here. You could use null instead of newline (tr , ’\0’,xargs -0) for additional safety. For ultimate safety, store files in env via yaml and echo the env in addition to null handling and all bases are covered.

I like this - seems like it might make it easier to debug issues later too

something like a commented out debug line that writes the env contents into a file? is that possible/useful?

I'm not sure what it would specifically look like or if it's acat orecho (printf?) thing, but something like:

cat<<<"$changed-files">"list-changed-files.txt"

@mafredri I am leaving the suggestions here out of this PR. I need to learn the risks here and can address them in a follow-up PR. I also welcome you taking a jab at this.

Does this file support json comment syntax? If yes, might be nice to detail why we change some of these rules. Otherwise it's could be nice to stick to stock settings as close as possible, given that it has sane defaults.

Will add comments and convert to*.jsonc.

I see prettier was removed here, but no alternative given it its place?

./e2e/provisionerGenerated.ts is a generated file so should not format I guess.
This is already in the ignore list of biome.

These files must not be changed, probably best to not touch anything in anytestdata folder. Although, if they changed as a result of changing the Go files then that's OK.

What is the best way to do that?
These files are generated from code and so does the API and CLI docs. And to make the docs follow the rules this is an artifact.

I will further explore how best to deal with this.

This file is incorrectly indented. It'll be annoying if a developer is making local changes here and the whole file is reformatted.

removing as we want to lint/fmt these files.