Skip to content

Commit 1e68fe4

Browse files
authored
Clarify description of GitHub Actions workflows
Rephrase explanation of GitHub Actions workflows for clarity.
1 parent d912ae7 commit 1e68fe4

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

src/content/11/en/part11b.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ lang: en
99

1010
Before we start playing with GitHub Actions, let's have a look at what they are and how do they work.
1111

12-
GitHub Actions work on a basis of [workflows](https://docs.github.com/en/free-pro-team@latest/actions/learn-github-actions/introduction-to-github-actions#workflows). A workflow is a series of [jobs](https://docs.github.com/en/free-pro-team@latest/actions/learn-github-actions/introduction-to-github-actions#jobs) that are run when a certain triggering [event](https://docs.github.com/en/free-pro-team@latest/actions/learn-github-actions/introduction-to-github-actions#events) happens. The jobs that are run then themselves contain instructions for what GitHub Actions should do.
12+
GitHub Actions operate on [workflows](https://docs.github.com/en/free-pro-team@latest/actions/learn-github-actions/introduction-to-github-actions#workflows). A workflow is a series of [jobs](https://docs.github.com/en/free-pro-team@latest/actions/learn-github-actions/introduction-to-github-actions#jobs) that run when a specific [event](https://docs.github.com/en/free-pro-team@latest/actions/learn-github-actions/introduction-to-github-actions#events) triggers them. Each job contains its own set of instructions that tell GitHub Actions what to do.
1313

1414
A typical execution of a workflow looks like this:
1515

0 commit comments

Comments
 (0)