Learn how to use dependencies between actions to build complex workflows.
- [Instructor] If we consider our example workflow … like a flowchart, we have two jobs … that are run in parallel … when the workflow is triggered by an event … like a push to the repository. … But let's say, for example, … that the first job produces some output … that the second job needs as input. … If they're running in parallel, … the second job might fail without that input. … So, you might be wondering, … how do we get the first job to run before the second job? … We can create that kind of dependency … by adding the needs attribute to the second job. … When we add the needs attribute to a job, … we include the job ID of one or more job … that must complete successfully before the job will run. … Back in our workflow, if we add the needs attribute … to job2 and follow it by the identifier for job1, … job2 becomes dependent on job1. … We can change our flowchart representation … to show this dependency. … Now, job1 must complete successfully … before job2 will run. … We can create even more complex dependencies …
- Creating an action
- Creating a workflow
- Adding actions to a workflow
- Using an action from a repository
- Developing a CI/CD pipeline with GitHub Actions
- Building custom actions
- Publishing an action to the GitHub Marketplace
Skill Level Beginner
1. Your First Action
Your first Action2m 31s
2. Connecting Actions with Workflows
3. Using Actions
4. Developing a CI/CD Workflow
5. Building Custom Actions
- Mark as unwatched
- Mark all as unwatched
Are you sure you want to mark all the videos in this course as unwatched?
This will not affect your course history, your reports, or your certificates of completion for this course.Cancel
Take notes with your new membership!
Type in the entry box, then click Enter to save your note.
1:30Press on any video thumbnail to jump immediately to the timecode shown.
Notes are saved with you account but can also be exported as plain text, MS Word, PDF, Google Doc, or Evernote.