setup-taskfile

This action makes the task binary available to Workflows.

DEPRECATION NOTICE

WARNING: the action has been moved to https://github.com/arduino/setup-task

This unmaintained copy is kept only to provide provisional support for existing workflows, but will be removed soon.

See the migration guide:

https://github.com/arduino/setup-task/releases/tag/v1.0.0

Usage

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

- name: Install Taskfile
  uses: Arduino/actions/setup-taskfile@master

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

- name: Install Taskfile
  uses: Arduino/actions/setup-taskfile@master
  with:
    version: '2.x'

To pin the exact version:

- name: Install Taskfile
  uses: Arduino/actions/setup-taskfile@master
  with:
    version: '2.6.1'

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

We check in the node_modules to provide runtime dependencies to the system using the Action, so be careful not to git add all the development dependencies you might have under your local node_modules. To release a new version of the Action the workflow should be the following:

1. npm install to add all the dependencies, included development.
2. npm run test to see everything works as expected.
3. npm run build to build the Action under the ./lib folder.
4. rm -rf node_modules to remove all the dependencies.
5. npm install --production to add back only the runtime dependencies.
6. git add lib node_modules to check in the code that matters.
7. open a PR and request a review.