trunk can also be managed by the
.trunk/user.yaml file in your repository. This file is optional, but it allows individual developers to customize how they want
trunk to run on their machines.
.trunk/user.yaml as you would for
.trunk/trunk.yaml. Now you can add additional linters, enable actions, or specify default command options, without impacting the way other developers run
Be mindful that
.trunk/user_trunk.yaml takes precedence over
.trunk/trunk.yaml, so substantial modifications could violate hermeticity.
Trunk also saves a user config in
$HOME/.cache/trunk/user.yaml. This is initially auto-generated, but some fields can be user-configured.
Trunk will periodically tell you to upgrade to a newer version if one is available. If you prefer not to see these notifications, edit (or add) the section of your
daemon and make sure it includes the following lines:
daemon: check_for_upgrades: false
This attribute defaults to true if not explicitly set. (Note: This key was
check_for_upgrade in the past).
Updated about 1 month ago