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: content/actions/concepts/workflows-and-actions/about-custom-actions.md
+1Lines changed: 1 addition & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,6 @@
1
1
---
2
2
title: About custom actions
3
+
shortTitle: Custom actions
3
4
intro: '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 {% data variables.product.prodname_dotcom %} community.'
Copy file name to clipboardExpand all lines: content/actions/concepts/workflows-and-actions/reusable-workflows.md
+9-1Lines changed: 9 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -36,7 +36,15 @@ Reusable workflows and composite actions both help you to avoid duplication. Whe
36
36
37
37
## Reusable workflows and workflow templates
38
38
39
-
Workflow templates allow everyone in your organization who has permission to create workflows to do so more quickly and easily. When people create a new workflow, they can choose a workflow template and some or all of the work of writing the workflow will be done for them. Within a workflow template, you can also reference reusable workflows to make it easy for people to benefit from reusing centrally managed workflow code. If you use a commit SHA when referencing the reusable workflow, you can ensure that everyone who reuses that workflow will always be using the same YAML code. However, if you reference a reusable workflow by a tag or branch, be sure that you can trust that version of the workflow. For more information, see [AUTOTITLE](/actions/security-guides/security-hardening-for-github-actions#reusing-third-party-workflows).
39
+
Workflow templates allow everyone in your organization who has permission to create workflows to do so more quickly and easily. When people create a new workflow, they can choose a workflow template and some or all of the work of writing the workflow will be done for them. Within a workflow template, you can also reference reusable workflows to make it easy for people to benefit from reusing centrally managed workflow code.
40
+
41
+
If you use a commit SHA when referencing the reusable workflow, you can ensure that everyone who reuses that workflow will always be using the same YAML code. However, if you reference a reusable workflow by a tag or branch, be sure that you can trust that version of the workflow. For more information, see [AUTOTITLE](/actions/security-guides/security-hardening-for-github-actions#reusing-third-party-workflows).
42
+
43
+
{% data variables.product.github %} offers workflow templates for a variety of languages and tooling. When you set up workflows in your repository, {% data variables.product.github %} analyzes the code in your repository and recommends workflows based on the language and framework in your repository. For example, if you use Node.js, {% data variables.product.github %} will suggest a workflow template file that installs your Node.js packages and runs your tests. You can search and filter to find relevant workflow templates.
44
+
45
+
{% data reusables.actions.workflow-templates-categories %}
46
+
47
+
{% data reusables.actions.workflow-templates-repo-link %}
40
48
41
49
For more information, see [AUTOTITLE](/actions/using-workflows/creating-starter-workflows-for-your-organization).
You can [contact {% data variables.contact.github_support %}](/support/contacting-github-support) for assistance with {% data variables.product.prodname_actions %}.
Copy file name to clipboardExpand all lines: content/actions/how-tos/managing-workflow-runs-and-deployments/managing-workflow-runs/re-running-workflows-and-jobs.md
+16-32Lines changed: 16 additions & 32 deletions
Original file line number
Diff line number
Diff line change
@@ -13,11 +13,8 @@ versions:
13
13
ghec: '*'
14
14
---
15
15
16
-
{% data reusables.actions.enterprise-github-hosted-runners %}
17
-
18
-
## About re-running workflows and jobs
19
-
20
-
Re-running a workflow or jobs in a workflow uses the same `GITHUB_SHA` (commit SHA) and `GITHUB_REF` (Git ref) of the original event that triggered the workflow run. The workflow will use the privileges of the actor who initially triggered the workflow, not the privileges of the actor who initiated the re-run. You can re-run a workflow or jobs in a workflow for up to 30 days after the initial run. You cannot re-run jobs in a workflow once its logs have passed their retention limits. For more information, see [AUTOTITLE](/actions/learn-github-actions/usage-limits-billing-and-administration#artifact-and-log-retention-policy). When you re-run a workflow or jobs in a workflow, you can enable debug logging for the re-run. This will enable runner diagnostic logging and step debug logging for the re-run. For more information about debug logging, see [AUTOTITLE](/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging)
16
+
> [!NOTE]
17
+
> Re-run workflows use the privileges of the actor who initially triggered the workflow, not the privileges of the actor who initiated the re-run. The workflow will also use the same `GITHUB_SHA` (commit SHA) and `GITHUB_REF` (git ref) of the original event that triggered the workflow run.
21
18
22
19
## Re-running all the jobs in a workflow
23
20
@@ -30,7 +27,6 @@ Re-running a workflow or jobs in a workflow uses the same `GITHUB_SHA` (commit S
30
27
1. In the upper-right corner of the workflow, re-run jobs.
31
28
32
29
* If any jobs failed, select the **{% octicon "sync" aria-hidden="true" aria-label="sync" %} Re-run jobs** dropdown menu and click **Re-run all jobs**.
33
-
34
30
* If no jobs failed, click **Re-run all jobs**.
35
31
36
32
{% data reusables.actions.enable-debug-logging %}
@@ -39,32 +35,28 @@ Re-running a workflow or jobs in a workflow uses the same `GITHUB_SHA` (commit S
39
35
40
36
{% cli %}
41
37
42
-
{% data reusables.cli.cli-learn-more %}
43
-
44
-
To re-run a failed workflow run, use the `run rerun` subcommand. Replace `run-id` with the ID of the failed run that you want to re-run. If you don't specify a `run-id`, {% data variables.product.prodname_cli %} returns an interactive menu for you to choose a recent failed run.
38
+
1. To re-run a failed workflow run, use the `run rerun` subcommand, replacing `RUN_ID` with the ID of the failed run that you want to re-run. If you don't specify a `run-id`, {% data variables.product.prodname_cli %} returns an interactive menu for you to choose a recent failed run.
45
39
46
-
```shell
47
-
gh run rerun RUN_ID
48
-
```
40
+
```shell copy
41
+
gh run rerun RUN_ID
42
+
```
49
43
50
-
{% data reusables.actions.enable-debug-logging-cli %}
44
+
{% data reusables.actions.enable-debug-logging-cli %}
51
45
52
-
```shell
53
-
gh run rerun RUN_ID --debug
54
-
```
46
+
```shell copy
47
+
gh run rerun RUN_ID --debug
48
+
```
55
49
56
-
To view the progress of the workflow run, use the `run watch` subcommand and select the run from the interactive list.
50
+
1. To view the progress of the workflow run, use the `run watch` subcommand and selectthe run from the interactive list.
57
51
58
-
```shell
59
-
gh run watch
60
-
```
52
+
```shell copy
53
+
gh run watch
54
+
```
61
55
62
56
{% endcli %}
63
57
64
58
## Re-running failed jobs in a workflow
65
59
66
-
If any jobs in a workflow run failed, you can re-run just the jobs that failed. When you re-run failed jobs in a workflow, a new workflow run will start for all failed jobs and their dependents. Any outputs for any successful jobs in the previous workflow run will be used for the re-run. Any artifacts that were created in the initial run will be available in the re-run. Any deployment protection rules that passed in the previous run will automatically pass in the re-run.
67
-
68
60
{% webui %}
69
61
70
62
{% data reusables.repositories.navigate-to-repo %}
@@ -78,7 +70,7 @@ If any jobs in a workflow run failed, you can re-run just the jobs that failed.
78
70
79
71
{% cli %}
80
72
81
-
To re-run failed jobs in a workflow run, use the `run rerun` subcommand with the `--failed` flag. Replace `run-id` with the ID of the run for which you want to re-run failed jobs. If you don't specify a `run-id`, {% data variables.product.prodname_cli %} returns an interactive menu for you to choose a recent failed run.
73
+
To re-run failed jobsin a workflow run, use the `run rerun` subcommand with the `--failed` flag. Replace `RUN_ID` with the ID of the run for which you want to re-run failed jobs. If you don't specify a `run-id`, {% data variables.product.prodname_cli %} returns an interactive menu for you to choose a recent failed run.
82
74
83
75
```shell
84
76
gh run rerun RUN_ID --failed
@@ -94,8 +86,6 @@ gh run rerun RUN_ID --failed --debug
94
86
95
87
## Re-running a specific job in a workflow
96
88
97
-
When you re-run a specific job in a workflow, a new workflow run will start for the job and any dependents. Any outputs for any other jobs in the previous workflow run will be used for the re-run. Any artifacts that were created in the initial run will be available in the re-run. Any deployment protection rules that passed in the previous run will automatically pass in the re-run.
98
-
99
89
{% webui %}
100
90
101
91
{% data reusables.repositories.navigate-to-repo %}
@@ -110,7 +100,7 @@ When you re-run a specific job in a workflow, a new workflow run will start for
110
100
111
101
{% cli %}
112
102
113
-
To re-run a specific job in a workflow run, use the `run rerun` subcommand with the `--job` flag. Replace `job-id` with the ID of the job that you want to re-run.
103
+
To re-run a specific job in a workflow run, use the `run rerun` subcommand with the `--job` flag. Replace `JOB_ID` with the ID of the job that you want to re-run.
114
104
115
105
```shell
116
106
gh run rerun --job JOB_ID
@@ -124,14 +114,8 @@ gh run rerun --job JOB_ID --debug
124
114
125
115
{% endcli %}
126
116
127
-
## Re-running workflows and jobs with reusable workflows
128
-
129
-
{% data reusables.actions.partial-reruns-with-reusable %}
130
-
131
117
## Reviewing previous workflow runs
132
118
133
-
You can view the results from your previous attempts at running a workflow. You can also view previous workflow runs using the API. For more information, see [AUTOTITLE](/rest/actions/workflow-runs#get-a-workflow-run).
134
-
135
119
{% data reusables.repositories.navigate-to-repo %}
136
120
{% data reusables.repositories.actions-tab %}
137
121
{% data reusables.repositories.navigate-to-workflow %}
0 commit comments