GitHub Action that installs the datamitsu CLI, provisions the tools your repository's config declares, and runs datamitsu in CI — in a single step.
steps:
- uses: actions/checkout@v4
- uses: datamitsu/setup-datamitsu@v0.1.5That installs datamitsu 0.1.5 and runs datamitsu init to provision the managed
tools your config declares. By default it then runs datamitsu lint (override
with args). The action carries no configuration of its own — it reads the
datamitsu config already in your repository.
Run a different command, or only set up the CLI:
# Run an arbitrary datamitsu command instead of `lint`
- uses: datamitsu/setup-datamitsu@v0.1.5
with:
args: "exec golangci-lint run ./..."
# Install + init only (put `datamitsu` on PATH, run nothing)
- uses: datamitsu/setup-datamitsu@v0.1.5
with:
args: ""Each release tag pins one datamitsu version: @v0.1.5 installs datamitsu
0.1.5. The SHA-256 hashes of every release binary are baked into that tag
(inlined in the non-minified dist/index.mjs) and verified on download — an
unverified or missing hash makes the action fail.
Pin by full version (@v0.1.5) or commit SHA, not a moving major tag, and
let Dependabot keep it
current:
# .github/dependabot.yml
version: 2
updates:
- package-ecosystem: "github-actions"
directory: "/"
schedule:
interval: "weekly"| Input | Default | Description |
|---|---|---|
args |
lint |
Arguments passed to datamitsu after setup. An empty string installs and initializes only. |
init |
true |
Run datamitsu init after install to provision managed tools. |
| Output | Description |
|---|---|
version |
The datamitsu version that was installed. |
This repository is auto-generated from
datamitsu/datamitsu (the
packaging/action package) on every datamitsu release. Do not edit it by hand.
Open issues and pull requests in the main repository.
Full documentation: https://datamitsu.com/docs/how-to/use-in-github-actions