Skip to content

Commit 9e89413

Browse files
authored
Merge pull request #18184 from github/repo-sync
repo sync
2 parents 10bf8fb + 5b09787 commit 9e89413

File tree

15 files changed

+75
-25
lines changed

15 files changed

+75
-25
lines changed
Binary file not shown.
Binary file not shown.
Binary file not shown.
Loading

content/actions/managing-workflow-runs/re-running-workflows-and-jobs.md

Lines changed: 29 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ versions:
1717

1818
## About re-running workflows and jobs
1919

20-
Re-running a workflow{% if re-run-jobs %} or jobs in a workflow{% endif %} uses the same `GITHUB_SHA` (commit SHA) and `GITHUB_REF` (Git ref) of the original event that triggered the workflow run. You can re-run a workflow{% if re-run-jobs %} or jobs in a workflow{% endif %} for up to 30 days after the initial run.
20+
Re-running a workflow{% if re-run-jobs %} or jobs in a workflow{% endif %} uses the same `GITHUB_SHA` (commit SHA) and `GITHUB_REF` (Git ref) of the original event that triggered the workflow run. You can re-run a workflow{% if re-run-jobs %} or jobs in a workflow{% endif %} for up to 30 days after the initial run.{% if debug-reruns %} 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 "[Enabling debug logging](/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging)."{% endif %}
2121

2222
## Re-running all the jobs in a workflow
2323

@@ -37,6 +37,7 @@ Re-running a workflow{% if re-run-jobs %} or jobs in a workflow{% endif %} uses
3737
1. In the upper-right corner of the workflow, use the **Re-run jobs** drop-down menu, and select **Re-run all jobs**.
3838
![Re-run checks drop-down menu](/assets/images/help/repository/rerun-checks-drop-down-updated.png)
3939
{% endif %}
40+
{% data reusables.actions.enable-debug-logging %}
4041

4142
{% endwebui %}
4243

@@ -50,6 +51,15 @@ To re-run a failed workflow run, use the `run rerun` subcommand. Replace `run-id
5051
gh run rerun <em>run-id</em>
5152
```
5253

54+
{% if debug-reruns %}
55+
{% data reusables.actions.enable-debug-logging-cli %}
56+
57+
```shell
58+
gh run rerun <em>run-id</em> --debug
59+
```
60+
61+
{% endif %}
62+
5363
To view the progress of the workflow run, use the `run watch` subcommand and select the run from the interactive list.
5464

5565
```shell
@@ -71,6 +81,7 @@ If any jobs in a workflow run failed, you can re-run just the jobs that failed.
7181
{% data reusables.repositories.view-run %}
7282
1. In the upper-right corner of the workflow, use the **Re-run jobs** drop-down menu, and select **Re-run failed jobs**.
7383
![Re-run failed jobs drop-down menu](/assets/images/help/repository/rerun-failed-jobs-drop-down.png)
84+
{% data reusables.actions.enable-debug-logging %}
7485

7586
{% endwebui %}
7687

@@ -82,6 +93,14 @@ To re-run failed jobs in a workflow run, use the `run rerun` subcommand with the
8293
gh run rerun <em>run-id</em> --failed
8394
```
8495

96+
{% if debug-reruns %}
97+
{% data reusables.actions.enable-debug-logging-cli %}
98+
99+
```shell
100+
gh run rerun <em>run-id</em> --failed --debug
101+
```
102+
103+
{% endif %}
85104
{% endcli %}
86105

87106
## Re-running a specific job in a workflow
@@ -99,6 +118,7 @@ When you re-run a specific job in a workflow, a new workflow run will start for
99118

100119
Alternatively, click on a job to view the log. In the log, click {% octicon "sync" aria-label="The re-run icon" %}.
101120
![Re-run selected job](/assets/images/help/repository/re-run-single-job-from-log.png)
121+
{% data reusables.actions.enable-debug-logging %}
102122

103123
{% endwebui %}
104124

@@ -110,6 +130,14 @@ To re-run a specific job in a workflow run, use the `run rerun` subcommand with
110130
gh run rerun --job <em>job-id</em>
111131
```
112132

133+
{% if debug-reruns %}
134+
{% data reusables.actions.enable-debug-logging-cli %}
135+
136+
```shell
137+
gh run rerun --job <em>job-id</em> --debug
138+
```
139+
140+
{% endif %}
113141
{% endcli %}
114142

115143
{% endif %}

content/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -22,6 +22,12 @@ These extra logs are enabled by setting secrets in the repository containing the
2222

2323
For more information on setting secrets, see "[Creating and using encrypted secrets](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)."
2424

25+
{% if debug-reruns %}
26+
27+
Additionally, anyone who has access to run a workflow can enable runner diagnostic logging and step debug logging for a workflow re-run. For more information, see "[Re-running workflows and jobs](/actions/managing-workflow-runs/re-running-workflows-and-jobs)."
28+
29+
{% endif %}
30+
2531
## Enabling runner diagnostic logging
2632

2733
Runner diagnostic logging provides additional log files that contain information about how a runner is executing a job. Two extra log files are added to the log archive:

content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1199,6 +1199,16 @@ Action | Description
11991199
| `secret_scanning.disable` | An organization owner disabled secret scanning for all existing{% ifversion ghec %} private or internal{% endif %} repositories. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)."
12001200
| `secret_scanning.enable` | An organization owner enabled secret scanning for all existing{% ifversion ghec %} private or internal{% endif %} repositories.
12011201

1202+
{% if secret-scanning-alert-audit-log %}
1203+
### `secret_scanning_alert` category actions
1204+
1205+
| Action | Description
1206+
|------------------|-------------------
1207+
| `secret_scanning_alert.create` | {% data variables.product.prodname_dotcom %} detected a secret and created a {% data variables.product.prodname_secret_scanning %} alert. For more information, see "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/code-security/secret-scanning/managing-alerts-from-secret-scanning)."
1208+
| `secret_scanning_alert.reopen` | A user reopened a {% data variables.product.prodname_secret_scanning %} alert.
1209+
| `secret_scanning_alert.resolve` | A user resolved a {% data variables.product.prodname_secret_scanning %} alert.
1210+
{% endif %}
1211+
12021212
### `secret_scanning_new_repos` category actions
12031213

12041214
| Action | Description

content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research/apply-for-an-educator-or-researcher-discount.md

Lines changed: 0 additions & 21 deletions
Original file line numberDiff line numberDiff line change
@@ -32,27 +32,6 @@ For more information about personal accounts on {% data variables.product.produc
3232
{% data reusables.education.plan-to-use-github %}
3333
{% data reusables.education.submit-application %}
3434

35-
## Upgrading your organization
36-
37-
After your request for an educator or researcher discount has been approved, you can upgrade the organizations you use with your learning community to {% data variables.product.prodname_team %}, which allows unlimited users and private repositories with full features, for free. You can upgrade an existing organization or create a new organization to upgrade.
38-
39-
### Upgrading an existing organization
40-
41-
{% data reusables.education.upgrade-page %}
42-
{% data reusables.education.upgrade-organization %}
43-
44-
### Upgrading a new organization
45-
46-
{% data reusables.education.upgrade-page %}
47-
1. Click {% octicon "plus" aria-label="The plus symbol" %} **Create an organization**.
48-
![Create an organization button](/assets/images/help/education/create-org-button.png)
49-
3. Read the information, then click **Create organization**.
50-
![Create organization button](/assets/images/help/education/create-organization-button.png)
51-
4. Under "Choose your plan", click **Choose {% data variables.product.prodname_free_team %}**.
52-
5. Follow the prompts to create your organization.
53-
{% data reusables.education.upgrade-page %}
54-
{% data reusables.education.upgrade-organization %}
55-
5635
## Further reading
5736

5837
- "[Why wasn't my application for an educator or researcher discount approved?](/articles/why-wasn-t-my-application-for-an-educator-or-researcher-discount-approved)"

content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -740,7 +740,19 @@ For more information, see "[Managing the publication of {% data variables.produc
740740
|------------------|-------------------
741741
| `disable` | Triggered when an organization owner disables secret scanning for all existing{% ifversion ghec %}, private or internal{% endif %} repositories. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)."
742742
| `enable` | Triggered when an organization owner enables secret scanning for all existing{% ifversion ghec %}, private or internal{% endif %} repositories.
743+
{% endif %}
744+
745+
{% if secret-scanning-alert-audit-log %}
746+
### `secret_scanning_alert` category actions
743747

748+
| Action | Description
749+
|------------------|-------------------
750+
| `create` | Triggered when {% data variables.product.prodname_dotcom %} detects an exposed secret and creates a {% data variables.product.prodname_secret_scanning %} alert. For more information, see "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/code-security/secret-scanning/managing-alerts-from-secret-scanning)."
751+
| `reopen` | Triggered when a user reopens a {% data variables.product.prodname_secret_scanning %} alert.
752+
| `resolve` | Triggered when a user resolves a {% data variables.product.prodname_secret_scanning %} alert.
753+
{% endif %}
754+
755+
{% ifversion ghec or ghes or ghae %}
744756
### `secret_scanning_new_repos` category actions
745757

746758
| Action | Description

data/features/debug-reruns.yml

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,7 @@
1+
# Issue 6629
2+
# Enabling debug logging when re-running jobs or workflows
3+
versions:
4+
fpt: '*'
5+
ghec: '*'
6+
ghes: '>=3.6'
7+
ghae: 'issue-6629'
Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
# Reference: #7046.
2+
# Documentation for new audit log events for alerts for secret scanning.
3+
versions:
4+
ghec: '*'
5+
ghes: '>=3.6'
6+
ghae: 'issue-7046'
Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
To enable enable runner diagnostic logging and step debug logging for the re-run, use the `--debug` flag.
Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,4 @@
1+
{% if debug-reruns %}
2+
1. Optionally, to enable runner diagnostic logging and step debug logging for the re-run, select **Enable debug logging**.
3+
![Enable debug logging](/assets/images/help/repository/enable-debug-logging.png)
4+
{% endif %}

data/reusables/education/upgrade-organization.md

Lines changed: 0 additions & 2 deletions
This file was deleted.

data/reusables/education/upgrade-page.md

Lines changed: 0 additions & 1 deletion
This file was deleted.

0 commit comments

Comments
 (0)