Git Hooks
Trunk supports triggering actions on all githooks
Features
Seamlessly bring
git-hooks
under version control.git-hooks
can be a major headache for organizations - they require manual installation and are not easily versioned along with the rest of your code.Take advantage of Trunk's powerful sandboxing and environment management to write and execute hooks using the programming language and runtime of your choice, as opposed to dealing with complicated bash scripts.
Manual Installation
Automatic Installation
Trunk will automatically install and begin managing your githooks
if you have any actions enabled in trunk.yaml
which trigger from git events.
Triggering an action from a githook
As an example let's examine how we implement the git-lfs
action in the plugins repo.
Definition
Template resolution
As documented by git, each githook generates a variable number of parameters that can be referenced in the run
entry for the action.
The following special variables are made available for template resolution when reacting to a git event:
Variable | Description |
---|---|
| Hook that triggered this action (e.g. |
| Positional parameters passed by |
| All parameters passed to the hook |
Interactivity
Setting interactive
to true will allow your githook action to be run from an interactive terminal. This enables you to write more complicated hooks to react to user input.
Testing a githook
action
githook
actionThe following command will simulate a githook event and execute all of the enabled actions for the provided hook in the order you defined them.
Alternatively, once an action is enabled you can call git
and debug with the actual git
provided data. This is sometimes easier since some git parameters point to txt files etc...and fabricating those formats through manual testing can be tricky.
Debugging a githook
action
githook
actionYou can observe the actions that are triggered by a git
event by calling:
Which will print out the last 10 executions including timestamps of the specified action \
Uninstalling
Remove all actions that are triggered by githooks from trunk.yaml
and run
Trunk Announce
Does your commit carry some important information to share with the rest of your organization? Now you can easily share it with the rest of the org by including /trunk announce
at the beginning of one of the lines of your commit message (if your org squashes commit messages, you should put it in your PR description). Any additional text on that line will form an optional title, and the remaining text of the commit message will form the commit body (both are optional, but either a title or body is required). These will then be displayed to other users when they pull or rebase.
If you want to see what your announcement would look like locally, just create a commit with the desired message and then run trunk show-announcements since HEAD~1
(trunk show-announcements since <ref>
will show all trunk announcements since the provided ref).
Just run trunk actions enable trunk-announce
to start using Trunk Announce.
Last updated