You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: learn-pr/github/github-actions-ci/includes/2-github-actions-workflows-ci.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ To implement this process, you learn how to:
5
5
- Create a workflow from a template.
6
6
- Avoid duplication by using reusable workflows.
7
7
- Identify the event that triggered a workflow.
8
-
-Understand GitHub Actions workflow logs.
8
+
-Use GitHub Actions workflow logs.
9
9
- Test against multiple targets.
10
10
- Separate build and test jobs.
11
11
- Save and access build artifacts.
@@ -82,7 +82,7 @@ A team of developers can benefit from using reusable workflows to streamline and
82
82
83
83
As teams scale and projects grow, it's common to see the same steps repeated across multiple workflow files. These steps might include code checkout, dependency installation, testing, and deployment. This kind of duplication not only clutters your code base but also increases maintenance time when code changes are required. Reusable workflows solve this problem by allowing you to define automation logic once, and then call the logic from other workflows.
84
84
85
-
Reusable workflows are special GitHub Actions workflows that other workflows can call, much like functions in programming. You create them to share repeated logic like build steps, testing procedures, or deployment strategies. After you create a reusable workflow, you can reference it from any other workflow in the same repository or even in different repositories.
85
+
Reusable workflows are special GitHub Actions workflows that other workflows can call, similar to functions in programming. You create them to share repeated logic like build steps, testing procedures, or deployment strategies. After you create a reusable workflow, you can reference it from any other workflow in the same repository or even in different repositories.
86
86
87
87
:::image type="content" source="../media/reusable-workflow.png" alt-text="Diagram that shows the concept of reusable workflows in GitHub Actions. Multiple repositories or workflows can reference a central workflow." border="false":::
88
88
@@ -115,7 +115,7 @@ Imagine that your organization has 10 microservices. All 10 microservices need t
115
115
- Lint code
116
116
- Deploy to a specific environment
117
117
118
-
Without reusable workflows, every repo contains duplicated logic that list the repeated steps in each workflow..
118
+
Without reusable workflows, every repo contains duplicated logic that list the repeated steps in each workflow.
0 commit comments