Workflow
| Component | Description |
|---|---|
| Action | Individual tasks that you combine as steps to create a job. Actions are the smallest portable building block of a workflow. To use an action in a workflow, you must include it as a step. |
| Artifact | Artifacts are the files created when you build and test your code. Artifacts might include binary or package files, test results, screenshots, or log files. Artifacts can be used by the other jobs in the workflow or deployed directly by the workflow. |
| Event | A specific activity that triggers a workflow run. |
| Job | A defined task made up of steps. Each job is run in a fresh instance of the virtual environment. Jobs can run at the same time in parallel or be dependent on the status of a previous job and run sequentially. |
| Runner | Any machine with the GitHub Actions runner application installed. You can use a runner hosted by GitHub or host your own runner. A runner waits for available jobs. Runners run one job at a time reporting the progress, logs, and final result back to GitHub. |
| Step | A step is a set of tasks performed by a job. Steps can run commands or actions. |
| Virtual Environment | The virtual environment of a GitHub-hosted runner includes the virtual machine's hardware configuration, operating system, and installed software. |
| Workflow | A configurable automated process that you can set up in your repository. Workflows are made up of one or more jobs and can be scheduled or activated by an event. |
Action metadata
Filename: action.yml This file contains 3 required fields:
- name
- description
- runs
- using
- main
Input
Input parameter for an action:
- description: required
- required: (true or false)
- default
- core.getInput("[name]")
Output
Output parameter of an action:
- core.setOutput("[name]")
- reference to output parameter of previous action in a workflow: @steps.[step_id].outputs.[name]
get rid of node_modules
- npm install command
- ncc build index.js
error handling
- core.setFailed(err.message);