Siddhartha Bagaria

Closing now, but can reopen if someone says something.

Closing as per above comment.

This issue is now obsolete because the emscripten toolchain has changed their approach.

There is not much for us to do here. People can already use Bazel packages as toolchain roots, as long as some convention around target names is followed.

https://github.blog/changelog/2023-10-30-accelerate-your-ci-cd-with-arm-based-hosted-runners-in-github-actions/

Shameless plug here; if you are looking to use YCM with bazel, you can use this tool to generate compile_commands.json: https://github.com/grailbio/bazel-compilation-database

@GregBowyer, are you still interested in pursuing this?

Closing now because of inactivity. We can reopen if needed.

[Trunk Check](https://trunk.io/products/check) is a very comprehensive meta-linter that covers most file types. It is a commercial offering (but free for small teams), and is in the same spirit as [pre-commit.ci](pre-commit.ci)....

Thanks. I sent a PR that works for this specific example. But I am not sure if I am matching all the conditions right. Will you be able to take...