From the course: Learning GitHub Actions: Event-Driven Automation for Your Codebase
Unlock this course with a free trial
Join today to access over 24,900 courses taught by industry experts.
Add actions to a workflow - GitHub Tutorial
From the course: Learning GitHub Actions: Event-Driven Automation for Your Codebase
Add actions to a workflow
- [Instructor] As we continue developing our workflow, we need to add steps with actions and commands. For an action, we specify the uses attribute. This executes the actions code in a new process on the runner. Because actions can contain code, multiple commands, and any dependencies needed by the code, actions can provide a great deal of functionality in a workflow. To add a command to our workflow, we specify the run attribute. This tells the step to execute a command using the default shell of the runner's operating system. For Ubuntu and Mac Os systems, the default shell is Bash, and for Windows systems, the default shell is PowerShell. Let's take a closer look at actions and commands. Actions can be sourced from three different locations, public Git repositories, the same repositories as the workflow that's calling the action, and last but not least, an action can be sourced as an image from a container registry like Docker Hub. To source an action from a public registry, the…
Contents
-
-
-
Create a workflow2m 27s
-
Add jobs and steps to a workflow3m 10s
-
(Locked)
Add actions to a workflow4m 49s
-
(Locked)
Run a workflow2m 45s
-
(Locked)
Add dependencies between jobs1m 52s
-
(Locked)
Specify branches for workflow events2m 22s
-
(Locked)
Workflow and action limits1m 35s
-
(Locked)
Solution: Develop a multi-job workflow2m 19s
-
-
-
-
-