Skip to content
This repository has been archived by the owner on Sep 1, 2022. It is now read-only.

Add runs-on details #29

Merged
merged 4 commits into from
Dec 9, 2020
Merged

Add runs-on details #29

Changes from 2 commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
e7baaae
Add runs-on details
Rfosu2k2 Sep 29, 2020
7167fa0
Update responses/05.0_trigger.md
Rfosu2k2 Nov 21, 2020
1915c4f
Merge branch 'main' into patch-1
parkerbxyz Dec 9, 2020
5886954
Merge branch 'main' into patch-1
parkerbxyz Dec 9, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions responses/05.0_trigger.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,6 +3,7 @@ Nice, you just added an action block to your workflow file! Here are some import
- `jobs:` is the base component of a workflow run
- `build:` is the identifier we're attaching to this job
- `name:` is the name of the job, this is displayed on GitHub when the workflow is running
- `runs-on:` defines the type of machine to run the job on. The machine can be either a GitHub-hosted runner or a self-hosted runner.
- `steps:` the linear sequence of operations that make up a job
- `uses: actions/checkout@v1` uses a community action called [`checkout`](https://github.com/actions/checkout) to allow the workflow to access the contents of the repository
- `uses: ./action-a` provides the relative path the action we've created in the `action-a` directory of the repository
Expand Down