lfarci / github-actions

Preparation resources for the GitHub Actions certification
0 stars 0 forks source link

Describe how actions, workflows, jobs, steps, runs, and the marketplace work together #9

Closed lfarci closed 5 months ago

lfarci commented 5 months ago

Actions: These are the smallest portable building blocks of a workflow. Actions are individual tasks that you can combine to create jobs and customize your workflow. You can create your own actions, or use and customize actions shared by the GitHub community.

Workflows: These are custom automated processes that you can set up in your repository to build, test, package, release, or deploy any code project on GitHub. Workflows are composed of one or more jobs and can be triggered by various GitHub events.

Jobs: Jobs are a set of steps that execute on the same runner. By default, a workflow with multiple jobs will run those jobs in parallel. You can also configure a workflow to run jobs sequentially.

Steps: A step is an individual task that can run commands or actions. A job configuration can have an unlimited number of steps. Each step in a job executes on the same runner, allowing the steps to share data with each other.

Runs: A run is an instance of your workflow that runs when the pre-configured event occurs. For example, every time someone pushes a commit, opens a pull request, or creates an issue, your workflow runs.

Marketplace: The GitHub Marketplace is a central location for you to find, share, and use actions built by the GitHub community. You can use actions from the Marketplace to create more powerful and complex workflows without having to write all the code yourself.