trunk in a git repo is as simple as running:
When initializing you can secure your trunk installation which will write the sha256 signatures of the trunk binary to the
trunk.yaml file. These signatures are verified by the Trunk Launcher to guarantee the binary has not been tampered with. To add this extra layer of protection to your
trunk setup init like this:
trunk init --lock
init scans the files in your repo and generates a
.trunk/trunk.yaml configuration file tailoring the
trunk check product to your repo. The scan will identify all the particular languages and technologies you use and automatically configure the correct set of static-analyzers, code security tools, linters and formatters to run.
init flow will also generate linter-specific config files for tools that require configuration and no configuration file already exists.
trunk is completely control through the
trunk.yaml file. If for example you are not using the
check tool you can safely remove the
lint section from the file.
If you want to run
trunk inside your repository but are not ready to roll it out team-wide you can run
trunk in what we call single-play mode. This will essentially hide the trunk configuration information from the repo and allow you to tweak/configure/setup
trunk without causing churn to your teammates.
# hide trunk from the repository trunk config hide
# share trunk with the repository trunk config share
Updated 3 months ago