trunk-io/Trunk Check

The official trunk.io GitHub action

View on GitHub

Trust Signals

Scorecard Score
not yet scored
Maintenance Recency
Stale
License
None
namedescriptionrequireddefault
trunk-pathPath to Trunk Launcher. If not provided, we'll look for it the repo root, `.trunk/bin` and `tools/`. If it can't be found anywhere and is not provided explicitly, we'll download it on demand.no
labelLabel to append to the check run name (useful if running Trunk Check on multiple platforms)no
argumentsExtra arguments to pass to trunkno
check-modeTrunk check mode. Leave unset to autodetect. Set to 'all' to check the entire repository. Set to 'populate_cache_only' in a dedicated workflow to populate the GitHub Actions cache with Trunk artifacts (see docs for more details).no
check-all-modeIf set to "hold-the-line", computes new/existing issues by comparing to previous upload.no""
check-run-idCheck run ID. If set, posts annotations using CheckService.no
cacheCache trunk downloads and results between runs. Caching is only needed when using ephemeral CI runners.notrue
cache-keyA key unique to the repo/branch this action is being run on (e.g. the repo name and branch)no
post-initSteps to run after auto-init / before checkno
github-tokenFor overriding github.tokenno
trunk-tokenYou can find a per-repo API token in the Trunk web app settings. This will cause results to be uploaded to the Trunk web app if this job is a scheduled job running on a branch, or if `check-mode` is set to 'all'.no
upload-seriesUpload series name, for when `trunk-token` is provided. If not provided, we'll use the branch name.no
save-annotationsSave annotations as an artifact instead of posting them from this action. This is neccesary if your repository will be used with forks as they will will not have permissions to upload annotations. By default forks will be auto-detected.noauto
post-annotationsPost annotations previously uploaded with the `save-annotations` option (specific to posting annotations from forks).nofalse
setup-depsInstall dependencies for trunk check that the trunk CLI does not manage. This is only necessary if you have Node dependencies in your package.json that your Node linters need (e.g. eslint dependencies, or @types packages).nofalse
debugInternal use onlynofalse
timeout-secondsTimeout seconds before we kill the long running trunk check process via unix timeout command. Default setting of 0 seconds disables the timeout.no0
cat-trunk-debug-logsOption to cat .trunk/logs/cli.log && .trunk/logs/daemon.lognofalse
lfs-checkoutOption to checkout LFS filesnotrue

no outputs