This may not be applicable to Trunk Check if it is primarily a protoc plugin to generate type stubs.

I have a github repo a location a/ , I also have b/ inside of a/ , thus a/b/ is the path I'm looking at, this make trunk stop working. When I move a/ and /b to separate location, trunk work again.

https://github.com/martis42/depend_on_what_you_use

It would be nice to be able to enable plugins with a command like: trunk check enable pylint pylint-django and this would edit trunk.yaml to match: lint: enabled: - pylint@X.X.X: packages: - python-django@X.X.X

Solidity is a language for smart contracts. Because it's mainly used to move value around, security is critical, and so is linting. Adding common linters like solhint to trunk would be very beneficial to our dev community.

I noticed when viewing the "issues" tab for a project in the web app that some network requests can be VERY slow in some cases. I've regularly seen the network request to https://api.trunk.io:5022/trunk.services.edge.proto.v1.EdgeService/GetCheckIssueCodeSummary take 15s or more to get a response from the server. In the worst case it was nearly 2 minutes.

Closely related to https://changelog.trunk.io/check/p/expose-hermetic-tools-to-shell , it'd be great if we could instead opt _out_ of runtimes and use versions of tools out of other version manger files (e.g, .tool-versions ) to enable parity with existing version managers in use.

This project I use a lot with my team currently. You might think about supporting something similar to this. https://github.com/antonbabenko/pre-commit-terraform

I knew you can work with WSL but native windows support will be great.

I think the trunk check, action, and fmt will move faster if the CLI tool is open-sourced. I would have contributed some fixes and features if the source was available to contribute to.