arduino/setup-taskfile

This action makes the task binary available to Workflows.

Inputs

version

The version of Task to install. Can be an exact version (e.g., 3.4.2) or a version range (e.g., 3.x).

Default: 3.x

repo-token

(Optional) GitHub access token used for GitHub API requests. Heavy usage of the action can result in workflow run failures caused by rate limiting. GitHub provides a more generous allowance for Authenticated API requests.

It will be convenient to use ${{ secrets.GITHUB_TOKEN }}.

Usage

To get the latest stable version of Task just add this step:

- name: Install Taskfile
  uses: arduino/setup-taskfile@main

If you want to pin a major or minor version you can use the .x wildcard:

- name: Install Taskfile
  uses: arduino/setup-taskfile@main
  with:
    version: '2.x'

To pin the exact version:

- name: Install Taskfile
  uses: arduino/setup-taskfile@main
  with:
    version: '2.6.1'

Security

If you think you found a vulnerability or other security-related bug in this project, please read our security policy and report the bug to our Security Team 🛡️ Thank you!

e-mail contact: security@arduino.cc

Development

To work on the codebase you have to install all the dependencies:

# npm install

To run the tests:

# npm run test

Enable verbose logging for a pipeline

Additional log events with the prefix ::debug:: can be enabled by setting the secret ACTIONS_STEP_DEBUG to true.

See step-debug-logs for reference.

Release

To release a new version of the Action the workflow should be the following:

1. npm install to install the dependencies.
2. npm run test to see everything works as expected.
3. npm run build to build the Action under the ./lib folder.
4. npm run pack to package for distribution
5. git add src dist to check in the code that matters.
6. open a PR and request a review.