Skip to content

Commit 72c5f0c

Browse files
authored
Enforce blanks around Markdown headings (#43041)
1 parent 1894994 commit 72c5f0c

File tree

51 files changed

+204
-1
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

51 files changed

+204
-1
lines changed

Diff for: content/actions/automating-builds-and-tests/about-continuous-integration.md

+1
Original file line numberDiff line numberDiff line change
@@ -51,6 +51,7 @@ For a definition of common terms, see "[AUTOTITLE](/actions/learn-github-actions
5151
Browse the complete list of CI starter workflow offered by {% data variables.product.company_short %} in the {% ifversion fpt or ghec %}[actions/starter-workflows](https://github.com/actions/starter-workflows/tree/main/ci) repository{% else %} `actions/starter-workflows` repository on {% data variables.location.product_location %}{% endif %}.
5252

5353
{% ifversion fpt or ghec %}
54+
5455
## Further reading
5556

5657
- "[AUTOTITLE](/billing/managing-billing-for-github-actions)"

Diff for: content/actions/examples/using-concurrency-expressions-and-a-test-matrix.md

+1
Original file line numberDiff line numberDiff line change
@@ -45,6 +45,7 @@ topics:
4545
| Running tests on the runner | `npm test`|
4646

4747
## Example workflow
48+
4849
The following workflow was created by the {% data variables.product.prodname_dotcom %} Docs Engineering team. The workflow runs tests against the code in a pull request. To review the latest version of this file in the [`github/docs`](https://github.com/github/docs) repository, see [`test.yml`](https://github.com/github/docs/blob/main/.github/workflows/test.yml).
4950

5051
```yaml annotate copy

Diff for: content/actions/hosting-your-own-runners/managing-self-hosted-runners/managing-access-to-self-hosted-runners-using-groups.md

+7
Original file line numberDiff line numberDiff line change
@@ -46,6 +46,7 @@ type: tutorial
4646
{% endif %}
4747

4848
{% ifversion ghec or ghes or ghae %}
49+
4950
## Changing which organizations can access a runner group
5051

5152
{%- ifversion fpt or ghec or ghes %}
@@ -110,12 +111,14 @@ You can edit the name of your runner groups at the enterprise and organization l
110111
- [Changing the name of an enterprise runner group](#changing-the-name-of-an-enterprise-runner-group)
111112

112113
### Changing the name of an organization runner group
114+
113115
{% endif %}
114116

115117
{% data reusables.actions.runner-groups-org-navigation %}
116118
{% data reusables.actions.changing-the-name-of-a-runner-group %}
117119

118120
{% ifversion ghes or ghec or ghae %}
121+
119122
### Changing the name of an enterprise runner group
120123

121124
{% data reusables.actions.runner-groups-enterprise-navigation %}
@@ -135,6 +138,7 @@ You can edit the name of your runner groups at the enterprise and organization l
135138
- [Moving an enterprise runner to a group](#moving-an-enterprise-runner-to-a-group)
136139

137140
### Moving an organization runner to a group
141+
138142
{% endif %}
139143

140144
{% data reusables.organizations.navigate-to-org %}
@@ -143,6 +147,7 @@ You can edit the name of your runner groups at the enterprise and organization l
143147
{% data reusables.actions.moving-a-runner-to-a-group %}
144148

145149
{% ifversion ghes or ghec or ghae %}
150+
146151
### Moving an enterprise runner to a group
147152

148153
{% data reusables.enterprise-accounts.access-enterprise %}
@@ -161,12 +166,14 @@ You can edit the name of your runner groups at the enterprise and organization l
161166
- [Removing a runner group from an enterprise](#removing-a-runner-group-from-an-enterprise)
162167

163168
### Removing a runner group from an organization
169+
164170
{% endif %}
165171

166172
{% data reusables.actions.runner-groups-org-navigation %}
167173
{% data reusables.actions.removing-a-runner-group %}
168174

169175
{% ifversion ghes or ghec or ghae %}
176+
170177
### Removing a runner group from an enterprise
171178

172179
{% data reusables.actions.runner-groups-enterprise-navigation %}

Diff for: content/actions/hosting-your-own-runners/managing-self-hosted-runners/using-labels-with-self-hosted-runners.md

+5
Original file line numberDiff line numberDiff line change
@@ -37,6 +37,7 @@ You can create custom labels for runners at the repository{% ifversion ghec or g
3737
{% data reusables.actions.self-hosted-runners-create-label-steps %}
3838

3939
{% ifversion ghec or ghes or ghae %}
40+
4041
### Creating a custom label for an enterprise runner
4142

4243
{% data reusables.enterprise-accounts.access-enterprise %}
@@ -46,6 +47,7 @@ You can create custom labels for runners at the repository{% ifversion ghec or g
4647
{% data reusables.actions.self-hosted-runners-create-label-steps %}
4748

4849
{% endif %}
50+
4951
## Assigning a label to a self-hosted runner
5052

5153
You can assign labels to self-hosted runners at the repository{% ifversion ghec or ghes or ghae %}, organization, and enterprise{% else %} and organization{% endif %} levels.
@@ -65,6 +67,7 @@ You can assign labels to self-hosted runners at the repository{% ifversion ghec
6567
{% data reusables.actions.self-hosted-runner-assign-label-steps %}
6668

6769
{% ifversion ghec or ghes or ghae %}
70+
6871
### Assigning a label to an enterprise runner
6972

7073
{% data reusables.enterprise-accounts.access-enterprise %}
@@ -75,6 +78,7 @@ You can assign labels to self-hosted runners at the repository{% ifversion ghec
7578
{% data reusables.actions.self-hosted-runner-assign-label-steps %}
7679

7780
{% endif %}
81+
7882
## Removing a custom label from a self-hosted runner
7983

8084
You can remove custom labels from self-hosted runners at the repository{% ifversion ghec or ghes or ghae %}, organization, and enterprise{% else %} and organization{% endif %} levels.
@@ -94,6 +98,7 @@ You can remove custom labels from self-hosted runners at the repository{% ifvers
9498
{% data reusables.actions.self-hosted-runner-remove-label-steps %}
9599

96100
{% ifversion ghec or ghes or ghae %}
101+
97102
### Removing a custom label from an enterprise runner
98103

99104
{% data reusables.enterprise-accounts.access-enterprise %}

Diff for: content/actions/using-github-hosted-runners/about-larger-runners/controlling-access-to-larger-runners.md

+7
Original file line numberDiff line numberDiff line change
@@ -50,6 +50,7 @@ For example, the following diagram has a runner group named `grp-ubuntu-20.04-16
5050
{% data reusables.actions.section-using-unique-names-for-runner-groups %}
5151

5252
{% ifversion ghec %}
53+
5354
## Changing which organizations can access a runner group
5455

5556
{% data reusables.actions.hosted-runner-security-admonition %}
@@ -112,12 +113,14 @@ You can rename runner groups at the enterprise and organization levels.
112113
- [Changing the name of an enterprise runner group](##changing-the-name-of-an-enterprise-runner-group)
113114

114115
### Changing the name of an organization runner group
116+
115117
{% endif %}
116118

117119
{% data reusables.actions.runner-groups-org-navigation %}
118120
{% data reusables.actions.changing-the-name-of-a-runner-group %}
119121

120122
{% ifversion ghec %}
123+
121124
### Changing the name of an enterprise runner group
122125

123126
{% data reusables.actions.runner-groups-enterprise-navigation %}
@@ -133,6 +136,7 @@ You can rename runner groups at the enterprise and organization levels.
133136
- [Moving an enterprise runner to a group](#moving-an-enterprise-runner-to-a-group)
134137

135138
### Moving an organization runner to a group
139+
136140
{% endif %}
137141

138142
{% data reusables.organizations.navigate-to-org %}
@@ -141,6 +145,7 @@ You can rename runner groups at the enterprise and organization levels.
141145
{% data reusables.actions.moving-a-runner-to-a-group %}
142146

143147
{% ifversion ghec %}
148+
144149
### Moving an enterprise runner to a group
145150

146151
{% data reusables.enterprise-accounts.access-enterprise %}
@@ -159,12 +164,14 @@ You can rename runner groups at the enterprise and organization levels.
159164
- [Removing a runner group from an enterprise](#removing-a-runner-group-from-an-enterprise)
160165

161166
### Removing a runner group from an organization
167+
162168
{% endif %}
163169

164170
{% data reusables.actions.runner-groups-org-navigation %}
165171
{% data reusables.actions.removing-a-runner-group %}
166172

167173
{% ifversion ghec %}
174+
168175
### Removing a runner group from an enterprise
169176

170177
{% data reusables.actions.runner-groups-enterprise-navigation %}

Diff for: content/actions/using-github-hosted-runners/about-larger-runners/managing-larger-runners.md

+8
Original file line numberDiff line numberDiff line change
@@ -10,6 +10,7 @@ redirect_from:
1010
---
1111

1212
{% ifversion ghec %}
13+
1314
## Adding a {% data variables.actions.hosted_runner %} to an enterprise
1415

1516
Enterprise owners can add {% data variables.actions.hosted_runner %}s to an enterprise and assign them to organizations. By default, when a {% data variables.actions.hosted_runner %} is created for an enterprise, it is added to a default runner group that all organizations in the enterprise have access to. While all organizations are granted access to the runner, the repositories in each organization **are not** granted access. For each organization, an organization owner must configure the runner group to specify which repositories have access to the enterprise runner. For more information, see "[Allowing repositories to access a runner group](#allowing-repositories-to-access-a-runner-group)."
@@ -69,6 +70,7 @@ You can edit the name of your {% data variables.actions.hosted_runner %}s.
6970
- [Changing the name of an enterprise runner](#changing-the-name-of-an-enterprise-runner)
7071

7172
### Changing the name of an organization runner
73+
7274
{% endif %}
7375

7476
{% data reusables.organizations.navigate-to-org %}
@@ -78,6 +80,7 @@ You can edit the name of your {% data variables.actions.hosted_runner %}s.
7880
{% data reusables.actions.rename-larger-runner %}
7981

8082
{% ifversion ghec %}
83+
8184
### Changing the name of an enterprise runner
8285

8386
{% data reusables.enterprise-accounts.access-enterprise %}
@@ -95,7 +98,9 @@ You can control the maximum number of jobs allowed to run concurrently for speci
9598
{% ifversion ghec %}
9699
- [Configuring autoscaling for an organization runner](#configuring-autoscaling-for-an-organization-runner)
97100
- [Configuring autoscaling for an enterprise runner](#configuring-autoscaling-for-an-enterprise-runner)
101+
98102
### Configuring autoscaling for an organization runner
103+
99104
{% endif %}
100105

101106
{% data reusables.organizations.navigate-to-org %}
@@ -105,6 +110,7 @@ You can control the maximum number of jobs allowed to run concurrently for speci
105110
{% data reusables.actions.configure-autoscaling-for-larger-runners %}
106111

107112
{% ifversion ghec %}
113+
108114
### Configuring autoscaling for an enterprise runner
109115

110116
{% data reusables.enterprise-accounts.access-enterprise %}
@@ -133,6 +139,7 @@ The number of available IP addresses in the assigned ranges does not restrict nu
133139
- [Creating static IP addresses for enterprise runners](#creating-static-ip-addresses-for-enterprise-runners)
134140

135141
### Creating static IP addresses for organization runners
142+
136143
{% endif %}
137144

138145
{% data reusables.organizations.navigate-to-org %}
@@ -142,6 +149,7 @@ The number of available IP addresses in the assigned ranges does not restrict nu
142149
{% data reusables.actions..networking-for-larger-runners %}
143150

144151
{% ifversion ghec %}
152+
145153
### Creating static IP addresses for enterprise runners
146154

147155
{% data reusables.enterprise-accounts.access-enterprise %}

Diff for: content/admin/backing-up-and-restoring-your-instance/configuring-backups-on-your-instance.md

+1
Original file line numberDiff line numberDiff line change
@@ -277,6 +277,7 @@ On an instance in a high-availability configuration, after you restore to new di
277277
To remediate after the restoration completes and before starting replication, you can tear down stale UUIDs using `ghe-repl-teardown`. If you need further assistance, contact {% data variables.contact.contact_ent_support %}.
278278
279279
{% ifversion backup-utilities-progress %}
280+
280281
## Monitoring backup or restoration progress
281282
282283
During a backup or restoration operation, you can use the `ghe-backup-progress` utility on your backup host to monitor the operation's progress. The utility prints the progress of each job sequentially.

Diff for: content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise.md

+1
Original file line numberDiff line numberDiff line change
@@ -107,6 +107,7 @@ Optionally, organization owners can further restrict the access policy of the ru
107107
For more information, see "[AUTOTITLE](/actions/hosting-your-own-runners/managing-self-hosted-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)."
108108

109109
## 5. Automatically scale your self-hosted runners
110+
110111
{% ifversion actions-runner-controller %}Optionally, you can use {% data variables.product.prodname_actions_runner_controller %} (ARC) to automatically scale self-hosted runners. {% data reusables.actions.actions-runner-controller-about-arc %}
111112

112113
{% else %}Optionally, you can build custom tooling to automatically scale the self-hosted runners for {% ifversion ghec or ghae %}your enterprise{% elsif ghes %}{% data variables.location.product_location %}{% endif %}. For example, your tooling can respond to webhook events from {% data variables.location.product_location %} to automatically scale a cluster of runner machines. For more information, see "[AUTOTITLE](/actions/hosting-your-own-runners/managing-self-hosted-runners/autoscaling-with-self-hosted-runners)."

Diff for: content/authentication/authenticating-with-a-passkey/signing-in-with-a-passkey.md

+1
Original file line numberDiff line numberDiff line change
@@ -31,5 +31,6 @@ Some authenticators allow passkeys to be used with nearby devices. For example,
3131
1. On your nearby device, follow the prompts to complete the authentication process. For example, if you are using an iPhone, you might perform FaceID or enter your passcode.
3232

3333
## Further reading
34+
3435
- [AUTOTITLE](/authentication/authenticating-with-a-passkey/about-passkeys)
3536
- [AUTOTITLE](/authentication/authenticating-with-a-passkey/managing-your-passkeys)

Diff for: content/authentication/keeping-your-account-and-data-secure/sudo-mode.md

+1
Original file line numberDiff line numberDiff line change
@@ -63,6 +63,7 @@ To confirm access for sudo mode, you {% ifversion totp-and-mobile-sudo-challenge
6363
{%- endif %}
6464

6565
{% ifversion passkeys %}
66+
6667
## Confirming access using a passkey
6768

6869
You must have a passkey registered to your account to confirm access to your account for sudo mode using a passkey. For more information, see "[AUTOTITLE](/authentication/authenticating-with-a-passkey/about-passkeys)" and "[AUTOTITLE](/authentication/authenticating-with-a-passkey/managing-your-passkeys)."

Diff for: content/authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication.md

+1
Original file line numberDiff line numberDiff line change
@@ -51,6 +51,7 @@ If you've set up a security key on your account, and your browser supports secur
5151
1. Select the appropriate option in the prompt. Depending on your security key configuration, you may type a PIN, complete a biometric prompt, or use a physical security key.
5252

5353
{% ifversion passkeys %}
54+
5455
### Using a passkey
5556

5657
If you have enabled 2FA, and you have added a passkey to your account, you can use the passkey to sign in. Since passkeys satisfy both password and 2FA requirements, you can complete your sign in with a single step. For more information, see "[AUTOTITLE](/authentication/authenticating-with-a-passkey/about-passkeys)" and "[AUTOTITLE](/authentication/authenticating-with-a-passkey/signing-in-with-a-passkey)."

Diff for: content/billing/managing-the-plan-for-your-github-account/downgrading-your-accounts-plan.md

+1
Original file line numberDiff line numberDiff line change
@@ -89,6 +89,7 @@ To reduce the number of paid seats your organization uses, you can remove member
8989
1. Review the information about your new payment on your next billing date, then click **Remove seats**.
9090

9191
{% ifversion ghec %}
92+
9293
## Downgrading your enterprise account's plan
9394

9495
Enterprise accounts are only available with {% data variables.product.prodname_enterprise %}, so it's not possible to downgrade an enterprise account to another plan.

Diff for: content/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/configuring-advanced-setup-for-code-scanning.md

+1
Original file line numberDiff line numberDiff line change
@@ -167,6 +167,7 @@ For information on bulk enablement, see "[AUTOTITLE](/code-security/code-scannin
167167

168168
{% endif %}
169169
{% ifversion ghes < 3.5 %}
170+
170171
## Reasons for the "Analysis not found" message
171172

172173
If you used a pull request to add {% data variables.product.prodname_code_scanning %} to the repository, you will initially see an "Analysis not found" message when you click **Details** on the "{% data variables.product.prodname_code_scanning_caps %} results / TOOL NAME" check in a pull request.

Diff for: content/code-security/code-scanning/enabling-code-scanning/configuring-default-setup-for-code-scanning-at-scale.md

+2
Original file line numberDiff line numberDiff line change
@@ -54,6 +54,7 @@ If the code in a repository changes to include {% ifversion code-scanning-defaul
5454

5555
{% endif %}
5656
{% ifversion org-enable-code-scanning %}
57+
5758
## Configuring default setup for all eligible repositories in an organization
5859

5960
Through the "Code security and analysis" page of your organization's settings, you can enable default setup for all eligible repositories in your organization. For more information on repository eligibility, see "[Eligible repositories for {% data variables.product.prodname_codeql %} default setup at scale](#eligible-repositories-default-setup)."
@@ -80,6 +81,7 @@ Through the "Code security and analysis" page of your organization's settings, y
8081
{% data variables.product.prodname_code_scanning_caps %} is configured at the repository level. For more information, see "[AUTOTITLE](/code-security/code-scanning/enabling-code-scanning/configuring-default-setup-for-code-scanning)."
8182
{% endif %}
8283
{% ifversion code-security-multi-repo-enablement %}
84+
8385
## Configuring default setup for a subset of repositories in an organization
8486

8587
Through security overview for your organization, you can find eligible repositories for default setup, then enable default setup across each of those repositories simultaneously. For more information on repository eligibility, see "[Eligible repositories for {% data variables.product.prodname_codeql %} default setup at scale](#eligible-repositories-default-setup)."

Diff for: content/code-security/code-scanning/managing-your-code-scanning-configuration/editing-your-configuration-of-default-setup.md

+2
Original file line numberDiff line numberDiff line change
@@ -26,6 +26,7 @@ If your codebase depends on a library or framework that is not recognized by the
2626
If you need to change any other aspects of your {% data variables.product.prodname_code_scanning %} configuration, consider configuring advanced setup. For more information, see "[AUTOTITLE](/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/configuring-advanced-setup-for-code-scanning)."
2727

2828
{% ifversion code-scanning-without-workflow-310 %}
29+
2930
## Customizing your existing configuration of default setup
3031

3132
{% data reusables.repositories.navigate-to-repo %}
@@ -38,6 +39,7 @@ If you need to change any other aspects of your {% data variables.product.prodna
3839
1. To update your configuration, as well as run an initial analysis of your code with the new configuration, click **Save changes**. All future analyses will use your new configuration.
3940

4041
{% else %}
42+
4143
## Changing the selected query suite for your configuration of default setup
4244

4345
{% data reusables.repositories.navigate-to-repo %}

Diff for: content/code-security/code-scanning/troubleshooting-code-scanning/out-of-disk-or-memory.md

+3
Original file line numberDiff line numberDiff line change
@@ -18,11 +18,14 @@ versions:
1818
On very large projects, you may see `Error: "Out of disk"` or `Error: "Out of memory"` on self-hosted runners when running {% data variables.product.prodname_codeql %}. In this case, you may need to increase the memory or disk space available on your runners. You can review the recommended hardware resources for running {% data variables.product.prodname_codeql %} to make sure your self-hosted runners meet those requirements. For more information, see "[AUTOTITLE](/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/recommended-hardware-resources-for-running-codeql)."
1919

2020
{% else %}
21+
2122
## Use self-hosted runners
2223

2324
Self-hosted runners offer more control of hardware, operating system, and software tools than {% data variables.product.company_short %}-hosted runners can provide. For more information, see "[AUTOTITLE](/actions/hosting-your-own-runners/managing-self-hosted-runners/about-self-hosted-runners)." You can review the recommended hardware resources for running {% data variables.product.prodname_codeql %} to make sure your self-hosted runners meet those requirements. For more information, see "[AUTOTITLE](/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/recommended-hardware-resources-for-running-codeql)."
2425

2526
{% ifversion actions-hosted-runners %}
27+
2628
## Use larger runners
29+
2730
You can use larger runners, which are {% data variables.product.company_short %}-hosted runners with more RAM, CPU, and disk space than standard runners. These runners have the runner application and other tools preinstalled. For more information about larger runners and the specifications you can use with them, see "[AUTOTITLE](/actions/using-github-hosted-runners/about-larger-runners)."{% endif %}
2831
{% endif %}

Diff for: content/code-security/codeql-cli/getting-started-with-the-codeql-cli/analyzing-your-code-with-codeql-queries.md

+1
Original file line numberDiff line numberDiff line change
@@ -131,6 +131,7 @@ $ codeql database analyze /codeql-dbs/example-repo \
131131
```
132132

133133
{% ifversion code-scanning-tool-status-page %}
134+
134135
### Adding file coverage information to your results for monitoring
135136

136137
You can optionally submit file coverage information to {% data variables.product.product_name %} for display on the {% data variables.code-scanning.tool_status_page %} for {% data variables.product.prodname_code_scanning %}. For more information about file coverage information, see "[AUTOTITLE](/code-security/code-scanning/managing-your-code-scanning-configuration/about-the-tool-status-page#how-codeql-defines-scanned-files)."

0 commit comments

Comments
 (0)