Deprecate GitHub Enterprise Server 3.16 (#61616)

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Author: heiskr

content/account-and-profile/how-tos/account-settings/index.md

@@ -17,14 +17,11 @@ versions:
 children:
   - /managing-security-and-analysis-features
   - /managing-your-tab-size-rendering-preference
-  - /permission-levels-for-a-project-board-owned-by-a-personal-account
   - /manage-cookie-preferences
   - /managing-accessibility-settings
   - /prepare-for-job-change
-  - /managing-access-to-your-personal-accounts-project-boards
   - /integrating-jira-with-your-personal-projects
   - /set-your-hiring-status
 shortTitle: Account settings
 contentType: how-tos
 ---
-

content/account-and-profile/how-tos/account-settings/integrating-jira-with-your-personal-projects.md

@@ -29,7 +29,5 @@ category:
 
 ## Next steps
 
-{% ifversion projects-v1 %}
-* [AUTOTITLE](/organizations/managing-organization-settings/integrating-jira-with-your-organization-project-board){% endif %}
 * [Connect Jira Cloud to GitHub](https://confluence.atlassian.com/adminjiracloud/connect-jira-cloud-to-github-814188429.html) in the Atlassian documentation
 * For reference information, see [AUTOTITLE](/account-and-profile/reference/personal-account-reference).

content/account-and-profile/how-tos/account-settings/managing-access-to-your-personal-accounts-project-boards.md

@@ -428,73 +428,6 @@ on:
   page_build
 ```
 
-{% ifversion projects-v1 %}
-
-## `project`
-
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| --------------------- | -------------- | ------------ | -------------|
-| [`project`](/webhooks-and-events/webhooks/webhook-events-and-payloads#project) | - `created`<br/>- `closed`<br/>- `reopened`<br/>- `edited`<br/>- `deleted`<br/> | Last commit on default branch | Default branch |
-
-> [!NOTE]
-> * {% data reusables.developer-site.multiple_activity_types %} The `edited` activity type refers to when a {% data variables.projects.projects_v1_board %}, not a column or card on the {% data variables.projects.projects_v1_board %}, is edited. For information about each activity type, see [AUTOTITLE](/webhooks-and-events/webhooks/webhook-events-and-payloads#project). {% data reusables.developer-site.limit_workflow_to_activity_types %}
-> * {% data reusables.actions.branch-requirement %}
-> * This event only occurs for projects owned by the workflow's repository, not for organization-owned or user-owned projects or for projects owned by another repository.
-
-Runs your workflow when a {% data variables.projects.projects_v1_board %} is created or modified. For activity related to cards or columns in a {% data variables.projects.projects_v1_board %}, use the [`project_card`](#project_card) or [`project_column`](#project_column) events instead. For more information about {% data variables.projects.projects_v1_boards %}, see [AUTOTITLE](/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards). For information about the {% data variables.projects.projects_v1_board %} APIs, see [AUTOTITLE](/graphql/reference/projects-classic#object-project) in the GraphQL API documentation or [AUTOTITLE](/rest/projects-classic).
-
-For example, you can run a workflow when a project has been `created` or `deleted`.
-
-```yaml
-on:
-  project:
-    types: [created, deleted]
-```
-
-## `project_card`
-
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| --------------------- | -------------- | ------------ | -------------|
-| [`project_card`](/webhooks-and-events/webhooks/webhook-events-and-payloads#project_card) | - `created`<br/>- `moved`<br/>- `converted` to an issue<br/>- `edited`<br/>- `deleted` | Last commit on default branch | Default branch |
-
-> [!NOTE]
-> * {% data reusables.developer-site.multiple_activity_types %} For information about each activity type, see [AUTOTITLE](/webhooks-and-events/webhooks/webhook-events-and-payloads#project_card). {% data reusables.developer-site.limit_workflow_to_activity_types %}
-> * {% data reusables.actions.branch-requirement %}
-> * This event only occurs for projects owned by the workflow's repository, not for organization-owned or user-owned projects or for projects owned by another repository.
-
-Runs your workflow when a card on a {% data variables.projects.projects_v1_board %} is created or modified. For activity related to {% data variables.projects.projects_v1_boards %} or columns in a {% data variables.projects.projects_v1_board %}, use the [`project`](#project) or [`project_column`](#project_column) event instead. For more information about {% data variables.projects.projects_v1_boards %}, see [AUTOTITLE](/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards). For information about the project card APIs, see [AUTOTITLE](/graphql/reference/projects-classic#object-projectcard) in the GraphQL API documentation or [AUTOTITLE](/rest/projects-classic/cards).
-
-For example, you can run a workflow when a project card has been `created` or `deleted`.
-
-```yaml
-on:
-  project_card:
-    types: [created, deleted]
-```
-
-## `project_column`
-
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| --------------------- | -------------- | ------------ | -------------|
-| [`project_column`](/webhooks-and-events/webhooks/webhook-events-and-payloads#project_column) | - `created`<br/>- `updated`<br/>- `moved`<br/>- `deleted` | Last commit on default branch | Default branch |
-
-> [!NOTE]
-> * {% data reusables.developer-site.multiple_activity_types %} For information about each activity type, see [AUTOTITLE](/webhooks-and-events/webhooks/webhook-events-and-payloads#project_column). {% data reusables.developer-site.limit_workflow_to_activity_types %}
-> * {% data reusables.actions.branch-requirement %}
-> * This event only occurs for projects owned by the workflow's repository, not for organization-owned or user-owned projects or for projects owned by another repository.
-
-Runs your workflow when a column on a {% data variables.projects.projects_v1_board %} is created or modified. For activity related to {% data variables.projects.projects_v1_boards %} or cards in a {% data variables.projects.projects_v1_board %}, use the [`project`](#project) or [`project_card`](#project_card) event instead. For more information about {% data variables.projects.projects_v1_boards %}, see [AUTOTITLE](/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards). For information about the project column APIs, see [AUTOTITLE](/graphql/reference/projects-classic#object-projectcolumn) in the GraphQL API documentation or [AUTOTITLE](/rest/projects-classic#columns).
-
-For example, you can run a workflow when a project column has been `created` or `deleted`.
-
-```yaml
-on:
-  project_column:
-    types: [created, deleted]
-```
-
-{% endif %}
-
 ## `public`
 
 | Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
@@ -845,7 +778,7 @@ jobs:
 > * The webhook payload available to GitHub Actions does not include the `added`, `removed`, and `modified` attributes in the `commit` object. You can retrieve the full commit object using the API. For information, see [AUTOTITLE](/graphql/reference/commits#object-commit) in the GraphQL API documentation or [AUTOTITLE](/rest/commits#get-a-commit).
 > * Events will not be created if more than 5,000 branches are pushed at once. Events will not be created for tags when more than three tags are pushed at once.
 
-Runs your workflow when you push a commit or tag, or when you create a repository from a template. This includes workflows that are not merged into the default branch. For more information, see [AUTOTITLE](/actions/reference/workflows-and-actions/events-that-trigger-workflows#running-your-workflow-only-when-a-push-to-specific-branches-occurs). 
+Runs your workflow when you push a commit or tag, or when you create a repository from a template. This includes workflows that are not merged into the default branch. For more information, see [AUTOTITLE](/actions/reference/workflows-and-actions/events-that-trigger-workflows#running-your-workflow-only-when-a-push-to-specific-branches-occurs).
 
 For example, you can run a workflow when the `push` event occurs.
 

content/account-and-profile/how-tos/account-settings/permission-levels-for-a-project-board-owned-by-a-personal-account.md

@@ -134,7 +134,7 @@ $ ghe-config app.github.rate-limiting-exempt-users "hubot github-actions[bot]"
 
 ### ghe-config-apply
 
-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. 
+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.
 
 ```shell
 ghe-config-apply
@@ -375,13 +375,9 @@ ghe-reactivate-admin-login
 
 ### ghe-saml-mapping-csv
 
-{% ifversion scim-for-ghes-ga %}
-
 > [!NOTE]
 > This utility does not work with configurations that use SAML with SCIM provisioning. For the SCIM version of this tool, please refer to [`ghe-scim-identities-csv` utility](#ghe-scim-identities-csv).
 
-{% endif %}
-
 This utility allows administrators to output or update the SAML `NameID` mappings for users on an instance. The utility can output a CSV file that lists all existing mappings. You can also update mappings for users on your instance by editing the resulting file, then using the utility to assign new mappings from the file.
 
 To output a CSV file containing a list of all user SAML `NameID` mappings on the instance, run the following command.
@@ -406,8 +402,6 @@ To update SAML mappings on the instance with new values from the file, run the f
 ghe-saml-mapping-csv -u -f /PATH/TO/FILE
 ```
 
-{% ifversion scim-for-ghes-ga %}
-
 ### ghe-scim-identities-csv
 
 > [!NOTE]
@@ -429,8 +423,6 @@ ghe-scim-identities-csv -f /PATH/TO/FILE
 
 We recommend writing to a file in `/data/user/tmp`.
 
-{% endif %}
-
 ### ghe-service-list
 
 This utility lists all of the services that have been started or stopped (are running or waiting) on your appliance.

content/actions/reference/workflows-and-actions/events-that-trigger-workflows.md

@@ -3,7 +3,7 @@ title: About the backup service for GitHub Enterprise Server
 shortTitle: About the backup service
 intro: Learn what the built-in backup service offers and how it differs from a High Availability replica.
 versions:
-  ghes: '>=3.17'
+  ghes: '*'
 contentType: concepts
 category:
   - Back up and upgrade your instance

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

@@ -3,7 +3,7 @@ title: Backup service settings reference
 shortTitle: Backup settings
 intro: Reference for all configurable options available in the Backup Service section of the {% data variables.enterprise.management_console %}.
 versions:
-  ghes: '>= 3.17'
+  ghes: '*'
 contentType: reference
 category:
   - Back up and upgrade your instance