Skip to content

Commit 737ac95

Browse files
Deprecate GHES 3.15 (#61022)
Co-authored-by: mc <42146119+mchammer01@users.noreply.github.com>
1 parent 93ac520 commit 737ac95

239 files changed

Lines changed: 134 additions & 1060068 deletions

File tree

Some content is hidden

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

.gitignore

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -110,3 +110,4 @@ translations/
110110
# Shared local volume (bufo)
111111
.local
112112
docs-ghes-3.14/
113+
docs-ghes-3.15/

content/actions/how-tos/manage-runners/use-actions-runner-controller/deploy-runner-scale-sets.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1226,7 +1226,7 @@ You can also use ARC with {% data variables.product.prodname_codeql %} to identi
12261226
12271227
To designate a runner scale set for {% data variables.product.prodname_dependabot %} updates or {% data variables.product.prodname_code_scanning %} with {% data variables.product.prodname_codeql %}, use a descriptive installation name in your Helm chart, such as `dependabot` or `code-scanning`. You can then set the `runs-on` value in your workflows to the installation name, and use the designated runner scale set for {% data variables.product.prodname_dependabot %} updates or {% data variables.product.prodname_code_scanning %} jobs.
12281228
1229-
If you're using default setup for {% data variables.product.prodname_code_scanning %}, the analysis will automatically look for a runner scale set with the installation name `code-scanning` {% ifversion code-scanning-default-setup-customize-labels %} but you can specify a custom name in the configuration, so that individual repositories can use different runner scale sets. See [AUTOTITLE](/code-security/code-scanning/enabling-code-scanning/configuring-default-setup-for-code-scanning#assigning-labels-to-runners){% endif %}.
1229+
If you're using default setup for {% data variables.product.prodname_code_scanning %}, the analysis will automatically look for a runner scale set with the installation name `code-scanning` but you can specify a custom name in the configuration, so that individual repositories can use different runner scale sets. See [AUTOTITLE](/code-security/code-scanning/enabling-code-scanning/configuring-default-setup-for-code-scanning#assigning-labels-to-runners).
12301230

12311231
> [!NOTE]
12321232
> The [Dependabot Action](https://github.com/github/dependabot-action) is used to run {% data variables.product.prodname_dependabot %} updates via {% data variables.product.prodname_actions %}. This action requires Docker as a dependency. For this reason, you can only use {% data variables.product.prodname_actions_runner_controller %} with {% data variables.product.prodname_dependabot %} when Docker-in-Docker (DinD) mode is enabled. For more information, see [AUTOTITLE](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/managing-self-hosted-runners-for-dependabot-updates#system-requirements-for-dependabot-runners) and [AUTOTITLE](/actions/hosting-your-own-runners/managing-self-hosted-runners-with-actions-runner-controller/deploying-runner-scale-sets-with-actions-runner-controller#using-docker-in-docker-or-kubernetes-mode-for-containers).

content/actions/reference/security/oidc.md

Lines changed: 2 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -313,8 +313,8 @@ To help improve security, compliance, and standardization, you can customize the
313313
Customizing the claims results in a new format for the entire `sub` claim, which replaces the default predefined `sub` format in the token described in [Example subject claims](#example-subject-claims).
314314

315315
> [!NOTE]
316-
> The `sub` claim uses the shortened form `repo` (for example, `repo:ORG-NAME/REPO-NAME`) instead of `repository` to reference the repository. {% ifversion fpt or ghec or ghes > 3.15 %}
317-
> Any `:` within the context value will be replaced with `%3A`. {% endif %}
316+
> The `sub` claim uses the shortened form `repo` (for example, `repo:ORG-NAME/REPO-NAME`) instead of `repository` to reference the repository.
317+
> Any `:` within the context value will be replaced with `%3A`.
318318
319319
The following example templates demonstrate various ways to customize the subject claim. To configure these settings on {% data variables.product.prodname_dotcom %}, admins use the REST API to specify a list of claims that must be included in the subject (`sub`) claim.
320320

@@ -437,8 +437,6 @@ or:
437437

438438
In your cloud provider's OIDC configuration, configure the `sub` condition to require a `repository_owner_id` claim that matches the required value.
439439

440-
{% ifversion fpt or ghec or ghes > 3.15 %}
441-
442440
#### Example: Context value with `:`
443441

444442
This example demonstrates how to handle context value with `:`. For example, when the job references an environment named `production:eastus`.
@@ -455,7 +453,6 @@ This example demonstrates how to handle context value with `:`. For example, whe
455453
```
456454

457455
In your cloud provider's OIDC configuration, configure the `sub` condition to require that claims must include a specific value for `environment` and `repository_owner`. For example: `"sub": "environment:production%3Aeastus:repository_owner:octo-org"`.
458-
{% endif %}
459456

460457
{% ifversion oidc-custom-properties %}
461458

content/admin/administering-your-instance/administering-your-instance-from-the-command-line/command-line-utilities.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -134,7 +134,7 @@ $ ghe-config app.github.rate-limiting-exempt-users "hubot github-actions[bot]"
134134

135135
### ghe-config-apply
136136

137-
This utility applies {% data variables.enterprise.management_console %} settings, reloads system services, prepares a storage device, reloads application services, and runs any pending database migrations. It is equivalent to clicking **Save settings** in the {% data variables.enterprise.management_console %}'s web UI or to sending a POST request to [the `/manage/v1/config/apply` endpoint](/rest/enterprise-admin/manage-ghes#trigger-a-ghe-config-apply-run). {% ifversion ghes > 3.15 %} Starting in version 3.16, this utility applies configuration changes conditionally to relevant settings. You can force it to run unconditionally by using `-f` flag. {% endif %}
137+
This utility applies {% data variables.enterprise.management_console %} settings, reloads system services, prepares a storage device, reloads application services, and runs any pending database migrations. It is equivalent to clicking **Save settings** in the {% data variables.enterprise.management_console %}'s web UI or to sending a POST request to [the `/manage/v1/config/apply` endpoint](/rest/enterprise-admin/manage-ghes#trigger-a-ghe-config-apply-run). Starting in version 3.16, this utility applies configuration changes conditionally to relevant settings. You can force it to run unconditionally by using `-f` flag.
138138

139139
```shell
140140
ghe-config-apply

content/admin/index.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Enterprise administrator documentation
33
shortTitle: Enterprise administrators
4-
intro: 'Documentation and guides for enterprise administrators{% ifversion ghes %}, system administrators,{% endif %} and security specialists who {% ifversion ghes %}deploy, {% endif %}configure{% ifversion ghes %},{% endif %} and manage {% data variables.product.prodname_enterprise %}.'
4+
intro: Documentation and guides for enterprise administrators{% ifversion ghes %}, system administrators,{% endif %} and security specialists who {% ifversion ghes %}deploy, {% endif %}configure{% ifversion ghes %},{% endif %} and manage {% data variables.product.prodname_enterprise %}.
55
redirect_from:
66
- /github/setting-up-and-managing-your-enterprise/managing-your-enterprise-account
77
- /github/setting-up-and-managing-your-enterprise
@@ -108,7 +108,7 @@ children:
108108
- /managing-github-apps-for-your-enterprise
109109
- /managing-github-actions-for-your-enterprise
110110
- /configuring-packages
111-
- /managing-code-security
112111
- /release-notes
113112
- /all-releases
114113
---
114+

content/admin/managing-code-security/index.md

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

content/admin/managing-code-security/managing-github-advanced-security-for-your-enterprise/index.md

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

content/admin/managing-code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise.md

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

content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity-in-your-enterprise/activity-dashboard.md

Lines changed: 0 additions & 37 deletions
This file was deleted.
Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,16 +1,17 @@
11
---
22
title: Exploring user activity in your enterprise
3-
intro: 'You can view user {% ifversion ghes%}and system {% endif %}activity with {% ifversion ghes%}dashboards, log forwarding, and {% endif %}webhooks.'
3+
intro: You can view user {% ifversion ghes%}and system {% endif %}activity with {% ifversion ghes%}dashboards, log forwarding, and {% endif %}webhooks.
44
versions:
55
ghec: '*'
66
ghes: '*'
77
children:
8-
- /activity-dashboard
98
- /accessing-reports-for-your-instance
109
- /viewing-push-logs
1110
- /log-forwarding
1211
- /managing-global-webhooks
1312
shortTitle: Explore user activity
1413
redirect_from:
1514
- /admin/monitoring-activity-in-your-enterprise/exploring-user-activity
15+
- /admin/monitoring-activity-in-your-enterprise/exploring-user-activity-in-your-enterprise/activity-dashboard
1616
---
17+

0 commit comments

Comments
 (0)