Overview

A plugins repository provides users the ability to expand the core capabilities of trunk check and trunk actions. A plugin repo contains a set of custom linter and action definitions.

Importing a plugin repository

By default trunk imports the trunk-io/plugins repository. To import a repo add it to the plugins list. Each repo requires a URI and ref.

plugins:
  sources:
    - id: trunk
      uri: https://github.com/trunk-io/plugins
      ref: v0.0.3
      import_to_global: true

Custom linters and actions

The root of a plugin repository has a trunk.yaml file where the linters and actions exported by that repository are enumerated. The plugin trunk.yaml file looks a lot like a standard trunk.yaml file with the addition of a special field required_trunk_version which indicates the minimum trunk version required to use that repo.

Beyond the required_trunk_version the definition of an action or linter is no different in a plugin repository.

Add a plugin repo to your trunk.yaml file

Contributing to a published plugin repository

Let's quickly walk through how to modify/add to an existing remote repository. In this case we'll make an edit to the trunk-io/plugins repository.

1. Clone the plugins repository to your local disk - git clone [email protected]:trunk-io/plugins.git
2. Add a local field to your trunk.yaml file to point your usage of the plugin repo to your local instance. When a plugin source includes a local field that will supercede the remote uri/ref values. This makes it easy to quickly iterate locally before pushing changes to the cloud.

plugins:
  sources:
    - id: trunk
      uri: https://github.com/trunk-io/plugins
      ref: v0.0.3
      local: /home/eli/Github/plugins

3. Edit the entries in the local version of the plugin repository.
4. Push your changes to the remote version of the plugin repo.
5. Remove the local field and point the ref of the remote repo to the newly landed changes.