GitHub workflows offer a wide range of capabilities, including niche features catering to specific use cases or scenarios. In this section, we’re going to talk through the capabilities in detail we mentioned before, which will provide you with a foundation-level knowledge of the capabilities and the chance to apply these new learnings.

Before we jump into the specifics, here is a quick reminder on the structure of a workflow and what it primarily consists of:

• Events/triggers: Workflows are triggered by specific events, such as pushing code to a branch, creating a pull request, calls via the GitHub API, or scheduling a cronjob.
• Jobs: A workflow can consist of multiple jobs, each running a sequence of steps. Jobs can run in parallel or sequentially, depending on your requirements.
• Steps: Each job consists of steps that perform individual tasks, such as running a script, checking out code, or using a pre-built action.

Now...