GitHub Actions: Difference between revisions
Jump to navigation
Jump to search
| Line 8: | Line 8: | ||
=Overview= | =Overview= | ||
GitHub Actions are event driven YAML-defined entities: you can run a series of commands in response to a specific event. These YAML files are stored in the repository in a directory called <code>.github/workflows</code>. An event automatically triggers a workflow, which contains a job. The job uses steps to control the order in which actions are run | GitHub Actions is a continuous integration and continuous delivery (CI/CD) platform that allows you to automate your build, test, and deployment pipeline. Individual actions are event driven YAML-defined entities: you can run a series of commands in response to a specific event. These YAML files are stored in the repository in a directory called <code>.github/workflows</code>. An event automatically triggers a workflow, which contains a job. The job uses steps to control the order in which actions are run. | ||
Revision as of 22:50, 27 October 2022
External
Internal
Overview
GitHub Actions is a continuous integration and continuous delivery (CI/CD) platform that allows you to automate your build, test, and deployment pipeline. Individual actions are event driven YAML-defined entities: you can run a series of commands in response to a specific event. These YAML files are stored in the repository in a directory called .github/workflows. An event automatically triggers a workflow, which contains a job. The job uses steps to control the order in which actions are run.