a673c41bcf
I originally set out to establish some logical order to the tasks on some indecipherable criteria. In the end, it resulted in a jumble. Alphabetical order is completely objective and it results in a fairly logical order in the end due to the the use of prefixes on the task names according to their domain. The exception is that the convenience "umbrella" tasks have been left at the top (in their own alphabetical order) so that they will have the maximum visibility as the most useful tasks. Even that is not completely inconsistent, since these don't have a namespace prefix, and so might be imagined to have a null global namespace prefix that would be sorted first.
arduino/setup-task
A GitHub Actions action that makes the Task task runner / build tool available to use in your workflow.
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 action's default version of Task just add this step:
- name: Install Task
uses: arduino/setup-task@v1
If you want to pin a major or minor version you can use the .x wildcard:
- name: Install Task
uses: arduino/setup-task@v1
with:
version: 2.x
To pin the exact version:
- name: Install Task
uses: arduino/setup-task@v1
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