Check

We currently support modifying the threshold at which a linter is blocking, but in the event where a linter only outputs high severity issues, we could have a mechanism to lower these programmatically

For example: actions: definitions: - id: start run: <command> trigger: - on: [shell-entry, shell-exit]

Check the hash of tools when they are downloaded beyond just pinning a version

https://github.com/autonomousapps/dependency-analysis-gradle-plugin

Hello Team, I wish to see sonarlint integrated as well in this tool

https://github.com/biomejs/biome

The output for error messages in the trunk cli seems to format multiple lines by filling in spaces to wrap to the end of the line. This is instead of just putting in a newline. In other words, a long list of messages in the ISSUES block is not actually multiple lines of text. Its one long line, and the end of each "line" has spaces filled in to the width that the CLI thinks the terminal is. This makes it impossible to cut and paste error messages into a text file. It also means if you resize your terminal the formatting goes crazy. It would be way simpler to just end lines with newlines.

It seems to correctly recognize that it needs the .ps1 script on Windows but then it doesn't call a full path and I think this is the issue. \Users\nwest\.cache\trunk\launcher\trunk.ps1 : The term '\Users\nwest\.cache\trunk\launcher\trunk.ps1' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again. At line:1 char:1 + \Users\nwest\.cache\trunk\launcher\trunk.ps1 init --vscode + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : ObjectNotFound: (\Users\nwest\.c...ncher\trunk.ps1:String) [], CommandNotFoundException + FullyQualifiedErrorId : CommandNotFoundException

Add trunk check integration in IntelliJ/WebStorm/GoLand/etc for code formatting and linter warnings