diff --git a/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions.md b/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions.md
index 59841f5ee1..d1f5fc820b 100644
--- a/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions.md
+++ b/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions.md
@@ -67,12 +67,11 @@ When you unwatch a repository, you unsubscribe from future updates from that rep
2. On the watched repositories page, after you've evaluated the repositories you're watching, choose whether to:
-
+
- Unwatch a repository
- Ignore all notifications for a repository
- If enabled, customize the types of event you receive notifications for ({% data reusables.notifications-v2.custom-notification-types %})
-
-{%- ifversion fpt or ghec or ghes or ghae > 3.3 %}
+
1. Optionally, to unsubscribe from all repositories owned by a given user or organization, select the **Unwatch all** dropdown and click the organization whose repositories you'd like to unsubscribe from. The button to unwatch all repositories is only available if you are watching all activity or custom notifications on over 10 repositories.
@@ -80,5 +79,3 @@ When you unwatch a repository, you unsubscribe from future updates from that rep
- Click **Unwatch** to confirm that you want to unwatch the repositories owned by the selected user or organization, or click **Cancel** to cancel.
-
-{% endif %}
diff --git a/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md b/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md
index 4a164cf90f..cfffcfc7e9 100644
--- a/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md
+++ b/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md
@@ -81,7 +81,7 @@ Anytime you comment in a conversation or when someone @mentions your username, y
{% ifversion update-notification-settings-22 %}For conversations you're watching or participating in, you can choose whether you want to receive notifications on {% data variables.product.company_short %} or by email in your notification settings. For more information, see "[AUTOTITLE](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications#choosing-your-notification-settings)."
-
+
{% else %}
@@ -151,19 +151,19 @@ Email notifications from {% data variables.location.product_location %} contain
- There are updates in repositories or team discussions you're watching or in a conversation you're participating in. For more information, see "[About participating and watching notifications](#about-participating-and-watching-notifications)."
- You gain access to a new repository or you've joined a new team. For more information, see "[Automatic watching](#automatic-watching)."
- There are new {% data variables.product.prodname_dependabot_alerts %} in your repository. For more information, see "[{% data variables.product.prodname_dependabot_alerts %} notification options](#dependabot-alerts-notification-options)." {% ifversion fpt or ghec %}
- - There are workflow runs updates on repositories set up with {% data variables.product.prodname_actions %}. For more information, see "[{% data variables.product.prodname_actions %} notification options](#github-actions-notification-options)."{% endif %}{% ifversion fpt or ghec or ghes or ghae > 3.3 %}
- - There are new deploy keys added to repositories that belong to organizations that you're an owner of. For more information, see "[Organization alerts notification options](#organization-alerts-notification-options)."{% endif %}
+ - There are workflow runs updates on repositories set up with {% data variables.product.prodname_actions %}. For more information, see "[{% data variables.product.prodname_actions %} notification options](#github-actions-notification-options)."{% endif %}
+ - There are new deploy keys added to repositories that belong to organizations that you're an owner of. For more information, see "[Organization alerts notification options](#organization-alerts-notification-options)."
## Automatic watching
-By default, anytime you gain access to a new repository, you will automatically begin watching that repository. Anytime you join a new team, you will automatically be subscribed to updates and receive notifications when that team is @mentioned. If you don't want to automatically be subscribed, you can unselect the automatic watching options in your notification settings.
+By default, anytime you gain access to a new repository, you will automatically begin watching that repository. Anytime you join a new team, you will automatically be subscribed to updates and receive notifications when that team is @mentioned. If you don't want to automatically be subscribed, you can unselect the automatic watching options in your notification settings.
{% ifversion update-notification-settings-22 %}
{% else %}
{% endif %}
-If "Automatically watch repositories" is disabled, then you will not automatically watch your own repositories. You must navigate to your repository page and choose the watch option.
+If "Automatically watch repositories" is disabled, then you will not automatically watch your own repositories. You must navigate to your repository page and choose the watch option.
For more information, see "[AUTOTITLE](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications#choosing-your-notification-settings)."
@@ -181,14 +181,14 @@ You can choose whether to watch or unwatch an individual repository. You can als
## Choosing where your organization’s email notifications are sent
-If you belong to an organization, you can choose the email account you want notifications for organization activity sent to. For example, if you belong to an organization for work, you may want your notifications sent to your work email address, rather than your personal address.
+If you belong to an organization, you can choose the email account you want notifications for organization activity sent to. For example, if you belong to an organization for work, you may want your notifications sent to your work email address, rather than your personal address.
{% data reusables.notifications-v2.email-notification-caveats %}
{% data reusables.notifications.access_notifications %}
{% data reusables.notifications-v2.manage-notifications %}
-3. Under "Default notification email", select the email address you'd like notifications sent to.
+3. Under "Default notification email", select the email address you'd like notifications sent to.
{% ifversion update-notification-settings-22 %}
@@ -197,11 +197,11 @@ If you belong to an organization, you can choose the email account you want noti
{% endif %}
{% ifversion ghes or ghae %}
-4. Click **Save**.{% endif %}
+4. Click **Save**.{% endif %}
-### Customizing email routes per organization
+### Customizing email routes per organization
-If you are a member of more than one organization, you can configure each one to send notifications to any of{% ifversion fpt or ghec %} your verified email addresses{% else %} the email addresses for your account{% endif %}. {% ifversion fpt or ghec %} For more information, see "[AUTOTITLE](/get-started/signing-up-for-github/verifying-your-email-address)."{% endif %}
+If you are a member of more than one organization, you can configure each one to send notifications to any of{% ifversion fpt or ghec %} your verified email addresses{% else %} the email addresses for your account{% endif %}. {% ifversion fpt or ghec %} For more information, see "[AUTOTITLE](/get-started/signing-up-for-github/verifying-your-email-address)."{% endif %}
{% data reusables.notifications.access_notifications %}
{% data reusables.notifications-v2.manage-notifications %}
@@ -218,24 +218,24 @@ If you are a member of more than one organization, you can configure each one to
-6. Select one of your verified email addresses, then click **Save**.
+6. Select one of your verified email addresses, then click **Save**.
{% else %}
3. Under "Custom routing," find your organization's name in the list.
- 
+ 
4. Click **Edit** next to the email address you want to change.
- 
+ 
-5. Select one of your verified email addresses, then click **Save**.
+5. Select one of your verified email addresses, then click **Save**.
{% endif %}
-## {% data variables.product.prodname_dependabot_alerts %} notification options
+## {% data variables.product.prodname_dependabot_alerts %} notification options
The notification options for your user account are available at [https://github.com/settings/notifications](https://github.com/settings/notifications). You can configure notification settings for each repository, in the repository watch settings.
@@ -256,12 +256,9 @@ Choose how you want to receive workflow run updates for repositories that you ar
{% ifversion ghes %}
{% endif %}
-{% ifversion fpt or ghec or ghes or ghae > 3.3 %}
-## Organization alerts notification options
+## Organization alerts notification options
-If you're an organization owner, you'll receive email notifications by default when organization members add new deploy keys to repositories within the organization. You can unsubscribe from these notifications. On the notification settings page, under "Organization alerts", unselect **Email**.
-
-{% endif %}
+If you're an organization owner, you'll receive email notifications by default when organization members add new deploy keys to repositories within the organization. You can unsubscribe from these notifications. On the notification settings page, under "Organization alerts", unselect **Email**.
{% ifversion fpt or ghes or ghec %}
## Managing your notification settings with {% data variables.product.prodname_mobile %}
@@ -290,7 +287,7 @@ You can also schedule when {% data variables.product.prodname_mobile %} will sen
3. To update your notification settings, tap **Configure Notifications** and then use the toggles to enable or disable your preferred types of push notifications.
4. Optionally, to schedule when {% data variables.product.prodname_mobile %} will send push notifications to your mobile device, tap **Working Hours**, use the **Custom working hours** toggle, and then choose when you would like to receive push notifications.
-## Configuring your watch settings for an individual repository with {% data variables.product.prodname_mobile %}
+## Configuring your watch settings for an individual repository with {% data variables.product.prodname_mobile %}
You can choose whether to watch or unwatch an individual repository. You can also choose to only be notified of {% ifversion fpt or ghec %}certain event types such as issues, pull requests, discussions (if enabled for the repository) and {% endif %}new releases, or completely ignore an individual repository.
diff --git a/content/actions/creating-actions/creating-a-javascript-action.md b/content/actions/creating-actions/creating-a-javascript-action.md
index 94c3550316..21a7c241ae 100644
--- a/content/actions/creating-actions/creating-a-javascript-action.md
+++ b/content/actions/creating-actions/creating-a-javascript-action.md
@@ -37,10 +37,9 @@ Once you complete this project, you should understand how to build your own Java
Before you begin, you'll need to download Node.js and create a public {% data variables.product.prodname_dotcom %} repository.
-1. Download and install Node.js {% ifversion fpt or ghes or ghae > 3.3 or ghec %}16.x{% else %}12.x{% endif %}, which includes npm.
-
- {% ifversion fpt or ghes or ghae > 3.3 or ghec %}https://nodejs.org/en/download/{% else %}https://nodejs.org/en/download/releases/{% endif %}
+1. Download and install Node.js 16.x, which includes npm.
+ https://nodejs.org/en/download/
1. Create a new public repository on {% data variables.location.product_location %} and call it "hello-world-javascript-action". For more information, see "[AUTOTITLE](/repositories/creating-and-managing-repositories/creating-a-new-repository)."
1. Clone your repository to your computer. For more information, see "[AUTOTITLE](/repositories/creating-and-managing-repositories/cloning-a-repository)."
@@ -73,7 +72,7 @@ outputs:
time: # id of output
description: 'The time we greeted you'
runs:
- using: {% ifversion fpt or ghes or ghae > 3.3 or ghec %}'node16'{% else %}'node12'{% endif %}
+ using: 'node16'
main: 'index.js'
```
diff --git a/content/actions/creating-actions/metadata-syntax-for-github-actions.md b/content/actions/creating-actions/metadata-syntax-for-github-actions.md
index dd1fd90d21..14a1bd7fa7 100644
--- a/content/actions/creating-actions/metadata-syntax-for-github-actions.md
+++ b/content/actions/creating-actions/metadata-syntax-for-github-actions.md
@@ -148,11 +148,11 @@ For more information on how to use context syntax, see "[AUTOTITLE](/actions/lea
**Required** Configures the path to the action's code and the runtime used to execute the code.
-### Example: Using Node.js {% ifversion fpt or ghes or ghae > 3.3 or ghec %}v16{% else %}v12{% endif %}
+### Example: Using Node.js v16
```yaml
runs:
- using: {% ifversion fpt or ghes or ghae > 3.3 or ghec %}'node16'{% else %}'node12'{% endif %}
+ using: 'node16'
main: 'main.js'
```
@@ -160,8 +160,7 @@ runs:
**Required** The runtime used to execute the code specified in [`main`](#runsmain).
-- Use `node12` for Node.js v12.{% ifversion fpt or ghes or ghae > 3.3 or ghec %}
-- Use `node16` for Node.js v16.{% endif %}
+- Use `node16` for Node.js v16.
### `runs.main`
@@ -175,7 +174,7 @@ In this example, the `pre:` action runs a script called `setup.js`:
```yaml
runs:
- using: {% ifversion fpt or ghes or ghae > 3.3 or ghec %}'node16'{% else %}'node12'{% endif %}
+ using: 'node16'
pre: 'setup.js'
main: 'index.js'
post: 'cleanup.js'
@@ -202,7 +201,7 @@ In this example, the `post:` action runs a script called `cleanup.js`:
```yaml
runs:
- using: {% ifversion fpt or ghes or ghae > 3.3 or ghec %}'node16'{% else %}'node12'{% endif %}
+ using: 'node16'
main: 'index.js'
post: 'cleanup.js'
```
@@ -262,7 +261,6 @@ For more information, see "[AUTOTITLE](/actions/learn-github-actions/contexts#gi
**Optional** The shell where you want to run the command. You can use any of the shells listed [here](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepsshell). Required if `run` is set.
-{% ifversion fpt or ghes or ghae > 3.3 or ghec %}
#### `runs.steps[*].if`
**Optional** You can use the `if` conditional to prevent a step from running unless a condition is met. You can use any supported context and expression to create a conditional.
@@ -291,7 +289,6 @@ steps:
if: {% raw %}${{ failure() }}{% endraw %}
uses: actions/heroku@1.0.0
```
-{% endif %}
#### `runs.steps[*].name`
diff --git a/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md b/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md
index 1de608ce5a..2589ff4501 100644
--- a/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md
+++ b/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md
@@ -46,13 +46,11 @@ You can set up automation to scale the number of self-hosted runners. For more i
You can add self-hosted runners to a single repository. To add a self-hosted runner to a user repository, you must be the repository owner. For an organization repository, you must be an organization owner or have admin access to the repository. For information about how to add a self-hosted runner with the REST API, see "[AUTOTITLE](/rest/actions#self-hosted-runners)."
-{% ifversion fpt or ghec or ghes or ghae > 3.3 %}
{% data reusables.repositories.navigate-to-repo %}
{% data reusables.repositories.sidebar-settings %}
{% data reusables.repositories.settings-sidebar-actions-runners %}
1. Click **New self-hosted runner**.
{% data reusables.actions.self-hosted-runner-configure %}
-{% endif %}
{% data reusables.actions.self-hosted-runner-check-installation-success %}
For more information, see "[AUTOTITLE](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners)."
@@ -61,13 +59,12 @@ For more information, see "[AUTOTITLE](/actions/hosting-your-own-runners/monitor
You can add self-hosted runners at the organization level, where they can be used to process jobs for multiple repositories in an organization. To add a self-hosted runner to an organization, you must be an organization owner. For information about how to add a self-hosted runner with the REST API, see "[AUTOTITLE](/rest/actions#self-hosted-runners)."
-{% ifversion fpt or ghec or ghes or ghae > 3.3 %}
+
{% data reusables.organizations.navigate-to-org %}
{% data reusables.organizations.org_settings %}
{% data reusables.organizations.settings-sidebar-actions-runners %}
{% ifversion actions-hosted-runners %}1. Click **New runner**, then click **New self-hosted runner**.{% else %}1. Click **New runner**.{% endif %}
{% data reusables.actions.self-hosted-runner-configure %}
-{% endif %}
{% data reusables.actions.self-hosted-runner-check-installation-success %}
For more information, see "[AUTOTITLE](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners)."
@@ -81,7 +78,7 @@ For more information, see "[AUTOTITLE](/actions/hosting-your-own-runners/monitor
{% ifversion ghec or ghes or ghae %}
New runners are assigned to the default group. You can modify the runner's group after you've registered the runner. For more information, see "[AUTOTITLE](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#moving-a-self-hosted-runner-to-a-group)."
-{% ifversion ghec or ghes or ghae > 3.3 %}
+{% ifversion ghec or ghes or ghae %}
To add a self-hosted runner to an enterprise, you must be an enterprise owner. For information about how to add a self-hosted runner with the REST API, see the enterprise endpoints in the [{% data variables.product.prodname_actions %} REST API](/rest/actions#self-hosted-runners).
diff --git a/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md b/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md
index c8632f43f7..f371e1f2a7 100644
--- a/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md
+++ b/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md
@@ -29,13 +29,11 @@ shortTitle: Remove self-hosted runners
To remove a self-hosted runner from a user repository you must be the repository owner. For an organization repository, you must be an organization owner or have admin access to the repository. We recommend that you also have access to the self-hosted runner machine. For information about how to remove a self-hosted runner with the REST API, see "[AUTOTITLE](/rest/actions#self-hosted-runners)."
{% data reusables.actions.self-hosted-runner-reusing %}
-{% ifversion fpt or ghec or ghes or ghae > 3.3 %}
{% data reusables.repositories.navigate-to-repo %}
{% data reusables.repositories.sidebar-settings %}
{% data reusables.repositories.settings-sidebar-actions-runners %}
{% data reusables.actions.settings-sidebar-actions-runner-selection %}
{% data reusables.actions.self-hosted-runner-removing-a-runner-updated %}
-{% endif %}
## Removing a runner from an organization
@@ -73,7 +71,7 @@ If you use {% data variables.product.prodname_ghe_cloud %}, you can also remove
To remove a self-hosted runner from an enterprise, you must be an enterprise owner. We recommend that you also have access to the self-hosted runner machine. For information about how to remove a self-hosted runner with the REST API, see the enterprise endpoints in the [{% data variables.product.prodname_actions %} REST API](/rest/actions#self-hosted-runners).
{% data reusables.actions.self-hosted-runner-reusing %}
-{% ifversion ghec or ghes or ghae > 3.3 %}
+{% ifversion ghec or ghes or ghae %}
{% data reusables.enterprise-accounts.access-enterprise %}
{% data reusables.enterprise-accounts.policies-tab %}
{% data reusables.enterprise-accounts.actions-tab %}
diff --git a/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md b/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md
index 638d43cc56..8cb27f5598 100644
--- a/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md
+++ b/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md
@@ -19,31 +19,25 @@ For information on how to use labels to route jobs to specific types of self-hos
## Creating a custom label
-{% ifversion fpt or ghec or ghes or ghae > 3.3 %}
{% data reusables.actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
{% data reusables.actions.settings-sidebar-actions-runner-selection %}
1. In the "Labels" section, click {% octicon "gear" aria-label="The Gear icon" %}.
1. In the "Find or create a label" field, type the name of your new label and click **Create new label**.
The custom label is created and assigned to the self-hosted runner. Custom labels can be removed from self-hosted runners, but they currently can't be manually deleted. {% data reusables.actions.actions-unused-labels %}
-{% endif %}
## Assigning a label to a self-hosted runner
-{% ifversion fpt or ghec or ghes or ghae > 3.3 %}
{% data reusables.actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
{% data reusables.actions.settings-sidebar-actions-runner-selection %}
{% data reusables.actions.runner-label-settings %}
- 1. To assign a label to your self-hosted runner, in the "Find or create a label" field, click the label.
-{% endif %}
+ 1. To assign a label to your self-hosted runner, in the "Find or create a label" field, click the label.
## Removing a custom label from a self-hosted runner
-{% ifversion fpt or ghec or ghes or ghae > 3.3 %}
{% data reusables.actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
{% data reusables.actions.settings-sidebar-actions-runner-selection %}
{% data reusables.actions.runner-label-settings %}
- 1. In the "Find or create a label" field, assigned labels are marked with the {% octicon "check" aria-label="The Check icon" %} icon. Click on a marked label to unassign it from your self-hosted runner.
-{% endif %}
+ 1. In the "Find or create a label" field, assigned labels are marked with the {% octicon "check" aria-label="The Check icon" %} icon. Click on a marked label to unassign it from your self-hosted runner.
## Programmatically assign labels
@@ -53,9 +47,9 @@ You can programmatically assign labels to a self-hosted runner after the runner
* To programmatically assign labels to a self-hosted runner during the initial runner configuration, you can pass label names to the `config` script using the `labels` parameter.
{% note %}
-
+
**Note:** You cannot use the `config` script to assign labels to an existing self-hosted runner.
-
+
{% endnote %}
For example, this command assigns a label named `gpu` when configuring a new self-hosted runner:
diff --git a/content/actions/learn-github-actions/contexts.md b/content/actions/learn-github-actions/contexts.md
index c283aaf8f6..82a1e48310 100644
--- a/content/actions/learn-github-actions/contexts.md
+++ b/content/actions/learn-github-actions/contexts.md
@@ -39,16 +39,14 @@ You can access contexts using the expression syntax. For more information, see "
{%- ifversion actions-configuration-variables %}
| `vars` | `object` | Contains variables set at the repository, organization, or environment levels. For more information, see [`vars` context](#vars-context). |{% endif %}
| `job` | `object` | Information about the currently running job. For more information, see [`job` context](#job-context). |
-{%- ifversion fpt or ghes or ghae > 3.3 or ghec %}
-| `jobs` | `object` | For reusable workflows only, contains outputs of jobs from the reusable workflow. For more information, see [`jobs` context](#jobs-context). |{% endif %}
+| `jobs` | `object` | For reusable workflows only, contains outputs of jobs from the reusable workflow. For more information, see [`jobs` context](#jobs-context). |
| `steps` | `object` | Information about the steps that have been run in the current job. For more information, see [`steps` context](#steps-context). |
| `runner` | `object` | Information about the runner that is running the current job. For more information, see [`runner` context](#runner-context). |
| `secrets` | `object` | Contains the names and values of secrets that are available to a workflow run. For more information, see [`secrets` context](#secrets-context). |
| `strategy` | `object` | Information about the matrix execution strategy for the current job. For more information, see [`strategy` context](#strategy-context). |
| `matrix` | `object` | Contains the matrix properties defined in the workflow that apply to the current job. For more information, see [`matrix` context](#matrix-context). |
| `needs` | `object` | Contains the outputs of all jobs that are defined as a dependency of the current job. For more information, see [`needs` context](#needs-context). |
-{%- ifversion fpt or ghec or ghes or ghae > 3.3 %}
-| `inputs` | `object` | Contains the inputs of a reusable {% ifversion actions-unified-inputs %}or manually triggered {% endif %}workflow. For more information, see [`inputs` context](#inputs-context). |{% endif %}
+| `inputs` | `object` | Contains the inputs of a reusable {% ifversion actions-unified-inputs %}or manually triggered {% endif %}workflow. For more information, see [`inputs` context](#inputs-context). |
As part of an expression, you can access context information using one of two syntaxes.
@@ -71,8 +69,6 @@ In addition, some functions may only be used in certain places. For example, the
The following table indicates where each context and special function can be used within a workflow. Unless listed below, a function can be used anywhere.
-{% ifversion fpt or ghes or ghae > 3.3 or ghec %}
-
| Workflow key | Context | Special functions |
| ---- | ------- | ----------------- |
{%- ifversion actions-run-name %}
@@ -110,38 +106,6 @@ The following table indicates where each context and special function can be use
| jobs.<job_id>.with.<with_id> | github, needs{% ifversion actions-reusable-workflow-matrix %}, strategy, matrix{% endif %}{% ifversion actions-unified-inputs %}, inputs{% endif %}{% ifversion actions-configuration-variables %}, vars{% endif %} | |
| on.workflow_call.inputs.<inputs_id>.default | github{% ifversion actions-unified-inputs %}, inputs{% endif %}{% ifversion actions-configuration-variables %}, vars{% endif %} | |
| on.workflow_call.outputs.<output_id>.value | github, jobs, {% ifversion actions-configuration-variables %}vars, {% endif %}inputs | |
-{% else %}
-| Path | Context | Special functions |
-| ---- | ------- | ----------------- |
-| concurrency | github | |
-| env | github, secrets | |
-| jobs.<job_id>.concurrency | github, needs, strategy, matrix | |
-| jobs.<job_id>.container | github, needs, strategy, matrix | |
-| jobs.<job_id>.container.credentials | github, needs, strategy, matrix, env, {% ifversion actions-configuration-variables %}vars, {% endif %}secrets | |
-| jobs.<job_id>.container.env.<env_id> | github, needs, strategy, matrix, job, runner, env, {% ifversion actions-configuration-variables %}vars, {% endif %}secrets | |
-| jobs.<job_id>.continue-on-error | github, needs, strategy, matrix | |
-| jobs.<job_id>.defaults.run | github, needs, strategy, matrix, env, {% ifversion actions-configuration-variables %}vars, {% endif %} | |
-| jobs.<job_id>.env | github, needs, strategy, matrix, secrets | |
-| jobs.<job_id>.environment | github, needs, strategy, matrix | |
-| jobs.<job_id>.environment.url | github, needs, strategy, matrix, job, runner, env, {% ifversion actions-configuration-variables %}vars, {% endif %}steps | |
-| jobs.<job_id>.if | github, needs | always, cancelled, success, failure |
-| jobs.<job_id>.name | github, needs, strategy, matrix | |
-| jobs.<job_id>.outputs.<output_id> | github, needs, strategy, matrix, job, runner, env, {% ifversion actions-configuration-variables %}vars, {% endif %}secrets, steps | |
-| jobs.<job_id>.runs-on | github, needs, strategy, matrix | |
-| jobs.<job_id>.services | github, needs, strategy, matrix | |
-| jobs.<job_id>.services.<service_id>.credentials | github, needs, strategy, matrix, env, {% ifversion actions-configuration-variables %}vars, {% endif %}secrets | |
-| jobs.<job_id>.services.<service_id>.env.<env_id> | github, needs, strategy, matrix, job, runner, env, {% ifversion actions-configuration-variables %}vars, {% endif %}secrets | |
-| jobs.<job_id>.steps.continue-on-error | github, needs, strategy, matrix, job, runner, env, {% ifversion actions-configuration-variables %}vars, {% endif %}secrets, steps | hashFiles |
-| jobs.<job_id>.steps.env | github, needs, strategy, matrix, job, runner, env, {% ifversion actions-configuration-variables %}vars, {% endif %}secrets, steps | hashFiles |
-| jobs.<job_id>.steps.if | github, needs, strategy, matrix, job, runner, env, {% ifversion actions-configuration-variables %}vars, {% endif %}steps | always, cancelled, success, failure, hashFiles |
-| jobs.<job_id>.steps.name | github, needs, strategy, matrix, job, runner, env, {% ifversion actions-configuration-variables %}vars, {% endif %}secrets, steps | hashFiles |
-| jobs.<job_id>.steps.run | github, needs, strategy, matrix, job, runner, env, {% ifversion actions-configuration-variables %}vars, {% endif %}secrets, steps | hashFiles |
-| jobs.<job_id>.steps.timeout-minutes | github, needs, strategy, matrix, job, runner, env, {% ifversion actions-configuration-variables %}vars, {% endif %}secrets, steps | hashFiles |
-| jobs.<job_id>.steps.with | github, needs, strategy, matrix, job, runner, env, {% ifversion actions-configuration-variables %}vars, {% endif %}secrets, steps | hashFiles |
-| jobs.<job_id>.steps.working-directory | github, needs, strategy, matrix, job, runner, env, {% ifversion actions-configuration-variables %}vars, {% endif %}secrets, steps | hashFiles |
-| jobs.<job_id>.strategy | github, needs | |
-| jobs.<job_id>.timeout-minutes | github, needs, strategy, matrix | |
-{% endif %}
### Example: printing context information to the log
@@ -207,11 +171,9 @@ The `github` context contains information about the workflow run and the event t
{%- endif %}
| `github.path` | `string` | Path on the runner to the file that sets system `PATH` variables from workflow commands. This file is unique to the current step and is a different file for each step in a job. For more information, see "[AUTOTITLE](/actions/using-workflows/workflow-commands-for-github-actions#adding-a-system-path)." |
| `github.ref` | `string` | {% data reusables.actions.ref-description %} |
-{%- ifversion fpt or ghec or ghes or ghae > 3.3 %}
| `github.ref_name` | `string` | {% data reusables.actions.ref_name-description %} |
| `github.ref_protected` | `boolean` | {% data reusables.actions.ref_protected-description %} |
| `github.ref_type` | `string` | {% data reusables.actions.ref_type-description %} |
-{%- endif %}
| `github.repository` | `string` | The owner and repository name. For example, `octocat/Hello-World`. |
{%- ifversion actions-oidc-custom-claims %}
| `github.repository_id` | `string` | {% data reusables.actions.repository_id-description %} |
@@ -227,9 +189,7 @@ The `github` context contains information about the workflow run and the event t
{%- ifversion fpt or ghec or ghes > 3.5 or ghae > 3.4 %}
| `github.run_attempt` | `string` | A unique number for each attempt of a particular workflow run in a repository. This number begins at 1 for the workflow run's first attempt, and increments with each re-run. |
{%- endif %}
-{%- ifversion fpt or ghec or ghes or ghae > 3.3 %}
| `github.secret_source` | `string` | The source of a secret used in a workflow. Possible values are `None`, `Actions`, `Dependabot`, or `Codespaces`. |
-{%- endif %}
| `github.server_url` | `string` | The URL of the GitHub server. For example: `https://github.com`. |
| `github.sha` | `string` | {% data reusables.actions.github_sha_description %} |
| `github.token` | `string` | A token to authenticate on behalf of the GitHub App installed on your repository. This is functionally equivalent to the `GITHUB_TOKEN` secret. For more information, see "[AUTOTITLE](/actions/security-guides/automatic-token-authentication)."
Note: This context property is set by the Actions runner, and is only available within the execution `steps` of a job. Otherwise, the value of this property will be `null`. |{% ifversion actions-stable-actor-ids %}
@@ -455,8 +415,6 @@ jobs:
- run: ./run-tests
```
-{% ifversion fpt or ghes or ghae > 3.3 or ghec %}
-
## `jobs` context
The `jobs` context is only available in reusable workflows, and can only be used to set outputs for a reusable workflow. For more information, see "[AUTOTITLE](/actions/using-workflows/reusing-workflows#using-outputs-from-a-reusable-workflow)."
@@ -527,8 +485,6 @@ jobs:
```
{% endraw %}
-{% endif %}
-
## `steps` context
The `steps` context contains information about the steps in the current job that have an [`id`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepsid) specified and have already run.
@@ -846,8 +802,6 @@ jobs:
- uses: {% data reusables.actions.action-checkout %}
- run: ./debug
```
-
-{% ifversion fpt or ghec or ghes or ghae > 3.3 %}
## `inputs` context
The `inputs` context contains input properties passed to an action{% ifversion actions-unified-inputs %},{% else %} or{% endif %} to a reusable workflow{% ifversion actions-unified-inputs %}, or to a manually triggered workflow{% endif %}. {% ifversion actions-unified-inputs %}For reusable workflows, the{% else %}The{% endif %} input names and types are defined in the [`workflow_call` event configuration](/actions/using-workflows/events-that-trigger-workflows#workflow-reuse-events) of a reusable workflow, and the input values are passed from [`jobs..with`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idwith) in an external workflow that calls the reusable workflow. {% ifversion actions-unified-inputs %}For manually triggered workflows, the inputs are defined in the [`workflow_dispatch` event configuration](/actions/using-workflows/events-that-trigger-workflows#workflow_dispatch) of a workflow.{% endif %}
@@ -933,5 +887,3 @@ jobs:
```
{% endraw %}
{% endif %}
-
-{% endif %}
diff --git a/content/actions/learn-github-actions/expressions.md b/content/actions/learn-github-actions/expressions.md
index 3c4e823bee..b92c8c3c53 100644
--- a/content/actions/learn-github-actions/expressions.md
+++ b/content/actions/learn-github-actions/expressions.md
@@ -283,14 +283,9 @@ Creates a hash for any `package-lock.json` and `Gemfile.lock` files in the repos
`hashFiles('**/package-lock.json', '**/Gemfile.lock')`
-{% ifversion fpt or ghes or ghae > 3.3 or ghec %}
## Status check functions
You can use the following status check functions as expressions in `if` conditionals. A default status check of `success()` is applied unless you include one of these functions. For more information about `if` conditionals, see "[AUTOTITLE](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idif)" and "[AUTOTITLE](/actions/creating-actions/metadata-syntax-for-github-actions#runsstepsif)".
-{% else %}
-## Check Functions
-You can use the following status check functions as expressions in `if` conditionals. A default status check of `success()` is applied unless you include one of these functions. For more information about `if` conditionals, see "[AUTOTITLE](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idif)".
-{% endif %}
### success
diff --git a/content/actions/learn-github-actions/understanding-github-actions.md b/content/actions/learn-github-actions/understanding-github-actions.md
index 9959b23894..12373a5aaf 100644
--- a/content/actions/learn-github-actions/understanding-github-actions.md
+++ b/content/actions/learn-github-actions/understanding-github-actions.md
@@ -52,7 +52,7 @@ You can configure a {% data variables.product.prodname_actions %} _workflow_ to
{% data reusables.actions.about-workflows-long %}
-{% ifversion fpt or ghes or ghae > 3.3 or ghec %}You can reference a workflow within another workflow, see "[AUTOTITLE](/actions/using-workflows/reusing-workflows)."{% endif %}
+You can reference a workflow within another workflow. For more information, see "[AUTOTITLE](/actions/using-workflows/reusing-workflows)."
For more information about workflows, see "[AUTOTITLE](/actions/using-workflows)."
diff --git a/content/actions/learn-github-actions/variables.md b/content/actions/learn-github-actions/variables.md
index 674ad48eda..69385a7300 100644
--- a/content/actions/learn-github-actions/variables.md
+++ b/content/actions/learn-github-actions/variables.md
@@ -259,11 +259,9 @@ We strongly recommend that actions use variables to access the filesystem rather
| `GITHUB_JOB` | The [job_id](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_id) of the current job. For example, `greeting_job`. |
| `GITHUB_PATH` | The path on the runner to the file that sets system `PATH` variables from workflow commands. This file is unique to the current step and changes for each step in a job. For example, `/home/runner/work/_temp/_runner_file_commands/add_path_899b9445-ad4a-400c-aa89-249f18632cf5`. For more information, see "[AUTOTITLE](/actions/using-workflows/workflow-commands-for-github-actions#adding-a-system-path)." |
| `GITHUB_REF` | {% data reusables.actions.ref-description %} |
-{%- ifversion fpt or ghec or ghes or ghae > 3.3 %}
| `GITHUB_REF_NAME` | {% data reusables.actions.ref_name-description %} |
| `GITHUB_REF_PROTECTED` | {% data reusables.actions.ref_protected-description %} |
| `GITHUB_REF_TYPE` | {% data reusables.actions.ref_type-description %} |
-{%- endif %}
| `GITHUB_REPOSITORY` | The owner and repository name. For example, `octocat/Hello-World`. |
{%- ifversion actions-oidc-custom-claims %}
| `GITHUB_REPOSITORY_ID` | {% data reusables.actions.repository_id-description %} |
diff --git a/content/actions/security-guides/encrypted-secrets.md b/content/actions/security-guides/encrypted-secrets.md
index 3248e0d5a5..b7b0c1b468 100644
--- a/content/actions/security-guides/encrypted-secrets.md
+++ b/content/actions/security-guides/encrypted-secrets.md
@@ -223,12 +223,8 @@ You can check which access policies are being applied to a secret in your organi
* {% data reusables.actions.forked-secrets %}
-{% ifversion fpt or ghec or ghes or ghae > 3.3 %}
-
* Secrets are not automatically passed to reusable workflows. For more information, see "[AUTOTITLE](/actions/using-workflows/reusing-workflows#passing-inputs-and-secrets-to-a-reusable-workflow)."
-{% endif %}
-
{% endnote %}
To provide an action with a secret as an input or environment variable, you can use the `secrets` context to access secrets you've created in your repository. For more information, see "[AUTOTITLE](/actions/learn-github-actions/contexts)" and "[AUTOTITLE](/actions/using-workflows/workflow-syntax-for-github-actions)."
@@ -426,7 +422,7 @@ You can use Base64 encoding to store small binary blobs as secrets. You can then
run: |
openssl x509 -in cert.der -inform DER -text -noout
```
-
+
{% note %}
**Note**: Using another shell might require different commands for decoding the secret to a file. On Windows runners, we recommend [using a bash shell](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepsshell) with `shell: bash` to use the commands in the `run` step above.
diff --git a/content/actions/security-guides/security-hardening-for-github-actions.md b/content/actions/security-guides/security-hardening-for-github-actions.md
index b0f64e330a..d006d8dfa4 100644
--- a/content/actions/security-guides/security-hardening-for-github-actions.md
+++ b/content/actions/security-guides/security-hardening-for-github-actions.md
@@ -186,11 +186,9 @@ You can help mitigate this risk by following these good practices:
Although pinning to a commit SHA is the most secure option, specifying a tag is more convenient and is widely used. If you’d like to specify a tag, then be sure that you trust the action's creators. The ‘Verified creator’ badge on {% data variables.product.prodname_marketplace %} is a useful signal, as it indicates that the action was written by a team whose identity has been verified by {% data variables.product.prodname_dotcom %}. Note that there is risk to this approach even if you trust the author, because a tag can be moved or deleted if a bad actor gains access to the repository storing the action.
-{% ifversion fpt or ghes or ghae > 3.3 or ghec %}
## Reusing third-party workflows
The same principles described above for using third-party actions also apply to using third-party workflows. You can help mitigate the risks associated with reusing workflows by following the same good practices outlined above. For more information, see "[AUTOTITLE](/actions/using-workflows/reusing-workflows)."
-{% endif %}
{% ifversion required-workflows %}
diff --git a/content/actions/using-workflows/about-workflows.md b/content/actions/using-workflows/about-workflows.md
index 4b0c042564..9eb595e499 100644
--- a/content/actions/using-workflows/about-workflows.md
+++ b/content/actions/using-workflows/about-workflows.md
@@ -193,10 +193,8 @@ To learn more about self-hosted runner labels, see "[AUTOTITLE](/actions/hosting
To learn more about {% data variables.product.prodname_dotcom %}-hosted runner labels, see "[AUTOTITLE](/actions/using-github-hosted-runners/about-github-hosted-runners#supported-runners-and-hardware-resources)."
{% endif %}
-{% ifversion fpt or ghes or ghae > 3.3 or ghec %}
### Reusing workflows
{% data reusables.actions.reusable-workflows %}
-{% endif %}
### Using environments
diff --git a/content/actions/using-workflows/creating-starter-workflows-for-your-organization.md b/content/actions/using-workflows/creating-starter-workflows-for-your-organization.md
index 7034b1c642..31d4671167 100644
--- a/content/actions/using-workflows/creating-starter-workflows-for-your-organization.md
+++ b/content/actions/using-workflows/creating-starter-workflows-for-your-organization.md
@@ -34,13 +34,11 @@ Starter workflows can be created by users with write access to the organization'
Starter workflows created by users can only be used to create workflows in public repositories. Organizations using {% data variables.product.prodname_ghe_cloud %} can also use starter workflows to create workflows in private repositories. For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/actions/using-workflows/creating-starter-workflows-for-your-organization).
{% endif %}
-{% ifversion fpt or ghes or ghae > 3.3 or ghec %}
{% note %}
**Note:** To avoid duplication among starter workflows you can call reusable workflows from within a workflow. This can help make your workflows easier to maintain. For more information, see "[AUTOTITLE](/actions/using-workflows/reusing-workflows)."
{% endnote %}
-{% endif %}
This procedure demonstrates how to create a starter workflow and metadata file. The metadata file describes how the starter workflows will be presented to users when they are creating a new workflow.
diff --git a/content/actions/using-workflows/events-that-trigger-workflows.md b/content/actions/using-workflows/events-that-trigger-workflows.md
index 3addc5ba62..3ff88804ec 100644
--- a/content/actions/using-workflows/events-that-trigger-workflows.md
+++ b/content/actions/using-workflows/events-that-trigger-workflows.md
@@ -1238,8 +1238,6 @@ on:
types: [started]
```
-{% ifversion fpt or ghes or ghae > 3.3 or ghec %}
-
### `workflow_call`
| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
@@ -1254,8 +1252,6 @@ The example below only runs the workflow when it's called from another workflow:
on: workflow_call
```
-{% endif %}
-
### `workflow_dispatch`
| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
@@ -1274,7 +1270,6 @@ You can configure custom-defined input properties, default input values, and req
{% data reusables.actions.inputs-vs-github-event-inputs %}
-{% ifversion fpt or ghec or ghes or ghae > 3.3 %}
This example defines inputs called `logLevel`, `tags`, and `environment`. You pass values for these inputs to the workflow when you run it. This workflow then prints the values to the log, using the {% ifversion actions-unified-inputs %}`inputs.logLevel`, `inputs.tags`, and `inputs.environment`{% else %}`github.event.inputs.logLevel`, `github.event.inputs.tags`, and `github.event.inputs.environment`{% endif %} context properties.
```yaml
@@ -1325,36 +1320,6 @@ gh workflow run run-tests.yml -f logLevel=warning -f tags=false -f environment=s
For more information, see the {% data variables.product.prodname_cli %} information in "[AUTOTITLE](/actions/managing-workflow-runs/manually-running-a-workflow)."
-{% else %}
-This example defines the `name` and `home` inputs and prints them using the {% ifversion actions-unified-inputs %}`inputs.name` and `inputs.home`{% else %}`github.event.inputs.name` and `github.event.inputs.home`{% endif %} contexts. If a `home` isn't provided, the default value 'The Octoverse' is printed.
-
-```yaml
-name: Manually triggered workflow
-on:
- workflow_dispatch:
- inputs:
- name:
- description: 'Person to greet'
- required: true
- default: 'Mona the Octocat'
- home:
- description: 'location'
- required: false
- default: 'The Octoverse'
-
-jobs:
- say_hello:
- runs-on: ubuntu-latest
- steps:
- - run: |
- echo Hello $NAME!
- echo -in $HOME
- env:
- NAME: {% ifversion actions-unified-inputs %}{% raw %}${{ inputs.name }}{% endraw %}{% else %}{% raw %}${{ github.event.inputs.name }}{% endraw %}{% endif %}
- HOME: {% ifversion actions-unified-inputs %}{% raw %}${{ github.event.inputs.home }}{% endraw %}{% else %}{% raw %}${{ github.event.inputs.home }}{% endraw %}{% endif %}
-```
-{% endif %}
-
### `workflow_run`
| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
diff --git a/content/actions/using-workflows/sharing-workflows-secrets-and-runners-with-your-organization.md b/content/actions/using-workflows/sharing-workflows-secrets-and-runners-with-your-organization.md
index b98aaa2704..590f8e1249 100644
--- a/content/actions/using-workflows/sharing-workflows-secrets-and-runners-with-your-organization.md
+++ b/content/actions/using-workflows/sharing-workflows-secrets-and-runners-with-your-organization.md
@@ -34,11 +34,9 @@ Your organization can share workflows by reusing the workflows exactly or by cre
{% data reusables.actions.internal-actions-summary %}
{% endif %}
-{% ifversion fpt or ghes or ghae > 3.3 or ghec %}
### Reusing workflows
{% data reusables.actions.reusable-workflows %}
-{% endif %}
### Using starter workflows
diff --git a/content/actions/using-workflows/triggering-a-workflow.md b/content/actions/using-workflows/triggering-a-workflow.md
index b381170e33..eba1a82d6d 100644
--- a/content/actions/using-workflows/triggering-a-workflow.md
+++ b/content/actions/using-workflows/triggering-a-workflow.md
@@ -121,15 +121,12 @@ You can use activity types and filters to further control when your workflow wil
{% data reusables.actions.workflow-dispatch-inputs %}
{% data reusables.actions.workflow-dispatch-inputs-example %}
-{% ifversion fpt or ghes or ghae > 3.3 or ghec %}
## Defining inputs, outputs, and secrets for reusable workflows
{% data reusables.actions.reusable-workflows-enterprise-beta %}
You can define inputs and secrets that a reusable workflow should receive from a calling workflow. You can also specify outputs that a reusable workflow will make available to a calling workflow. For more information, see "[AUTOTITLE](/actions/using-workflows/reusing-workflows)."
-{% endif %}
-
## Using event information
Information about the event that triggered a workflow run is available in the `github.event` context. The properties in the `github.event` context depend on the type of event that triggered the workflow. For example, a workflow triggered when an issue is labeled would have information about the issue and label.
diff --git a/content/actions/using-workflows/workflow-syntax-for-github-actions.md b/content/actions/using-workflows/workflow-syntax-for-github-actions.md
index 742efa032e..6d9b4ce7cf 100644
--- a/content/actions/using-workflows/workflow-syntax-for-github-actions.md
+++ b/content/actions/using-workflows/workflow-syntax-for-github-actions.md
@@ -68,7 +68,6 @@ run-name: Deploy to ${{ inputs.deploy_target }} by @${{ github.actor }}
{% data reusables.actions.workflows.section-triggering-a-workflow-schedule %}
-{% ifversion fpt or ghes or ghae > 3.3 or ghec %}
## `on.workflow_call`
{% data reusables.actions.reusable-workflows-enterprise-beta %}
@@ -192,7 +191,6 @@ A string identifier to associate with the secret.
#### `on.workflow_call.secrets..required`
A boolean specifying whether the secret must be supplied.
-{% endif %}
## `on.workflow_run.`
@@ -214,11 +212,9 @@ A boolean specifying whether the secret must be supplied.
A boolean specifying whether the input must be supplied.
-{% ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
#### `on.workflow_dispatch.inputs..type`
The value of this parameter is a string specifying the data type of the input. This must be one of: `boolean`, `choice`, `environment`, or `string`.
-{% endif %}
## `permissions`
@@ -980,7 +976,6 @@ Additional Docker container resource options. For a list of options, see "[`dock
{% endwarning %}
-{% ifversion fpt or ghes or ghae > 3.3 or ghec %}
## `jobs..uses`
{% data reusables.actions.reusable-workflows-enterprise-beta %}
@@ -1071,8 +1066,6 @@ jobs:
{% endraw %}
-{%endif%}
-
### `jobs..secrets.`
A pair consisting of a string identifier for the secret and the value of the secret. The identifier must match the name of a secret defined by [`on.workflow_call.secrets.`](#onworkflow_callsecretssecret_id) in the called workflow.
diff --git a/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise.md b/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise.md
index 103fed39ed..8bc919e8f9 100644
--- a/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise.md
+++ b/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise.md
@@ -99,18 +99,12 @@ You can create a runner group to manage access to the runner that you added to y
{% endwarning %}
{%- endif %}
{% data reusables.actions.create-runner-group %}
-{%- ifversion ghec or ghes or ghae > 3.3 %}
1. Click the "Runners" tab.
1. In the list of runners, click the runner that you deployed in the previous section.
1. Click **Edit**.
1. Click **Runner groups {% octicon "gear" aria-label="The Gear icon" %}**.
1. In the list of runner groups, click the name of the group that you previously created.
1. Click **Save** to move the runner to the group.
-{%- elsif ghae %}
-1. To the right of "Default", click the number of runners in the group to show the runners.
-1. Select the runner that you deployed.
-1. To the right of "Runner groups", select the **Move to group** dropdown, and click the group that you previously created.
-{%- endif %}
You've now deployed a self-hosted runner that can run jobs from {% data variables.product.prodname_actions %} within the organizations that you specified.
diff --git a/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md b/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md
index e0b878e600..73beb7b195 100644
--- a/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md
+++ b/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md
@@ -65,10 +65,8 @@ Think about how your enterprise can use features of {% data variables.product.pr
{% data reusables.actions.internal-actions-summary %}
-{% ifversion ghec or ghes or ghae > 3.3 %}
{% data reusables.actions.reusable-workflows-enterprise-beta %}
With reusable workflows, your team can call one workflow from another workflow, avoiding exact duplication. Reusable workflows promote best practice by helping your team use workflows that are well designed and have already been tested. For more information, see "[AUTOTITLE](/actions/using-workflows/reusing-workflows)."
-{% endif %}
To provide a starting place for developers building new workflows, you can use starter workflows. This not only saves time for your developers, but promotes consistency and best practice across your enterprise. For more information, see "[AUTOTITLE](/actions/using-workflows/creating-starter-workflows-for-your-organization)."
diff --git a/content/admin/user-management/managing-users-in-your-enterprise/removing-a-member-from-your-enterprise.md b/content/admin/user-management/managing-users-in-your-enterprise/removing-a-member-from-your-enterprise.md
index 02adda2736..eafdcbcdb5 100644
--- a/content/admin/user-management/managing-users-in-your-enterprise/removing-a-member-from-your-enterprise.md
+++ b/content/admin/user-management/managing-users-in-your-enterprise/removing-a-member-from-your-enterprise.md
@@ -12,12 +12,14 @@ shortTitle: Remove member
## About removal of enterprise members
-When you remove an enterprise member from your enterprise, the member is removed from all organizations owned by your enterprise.
+If you enterprise does not use {% data variables.product.prodname_emus %}, you can remove an enterprise member from {% data variables.product.prodname_dotcom %}. When you remove a member from your enterprise, the member is removed from all organizations owned by your enterprise.
If the enterprise member you're removing is the last owner of an organization owned by your enterprise, you will become an owner of that organization.
If your enterprise or any of the organizations owned by your enterprise uses an identity provider (IdP) to manage organization membership, the member may be added back to the organization by the IdP. Make sure to also make any necessary changes in your IdP.
+If your enterprise does use {% data variables.product.prodname_emus %}, you must remove the enterprise members through your identity provider (IdP) and the SCIM integration instead. For more information, see "[AUTOTITLE](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users#about-organization-membership-management)."
+
## Removing a member from your enterprise
{% note %}
diff --git a/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/customizing-code-scanning.md b/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/customizing-code-scanning.md
index a480ef6bba..f9e88bbaf1 100644
--- a/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/customizing-code-scanning.md
+++ b/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/customizing-code-scanning.md
@@ -528,7 +528,7 @@ For more information about using `exclude` and `include` filters in your custom
### Specifying directories to scan
-For the interpreted languages that {% data variables.product.prodname_codeql %} supports (Python{% ifversion fpt or ghes or ghae > 3.3 %}, Ruby{% endif %} and JavaScript/TypeScript), you can restrict {% data variables.product.prodname_code_scanning %} to files in specific directories by adding a `paths` array to the configuration file. You can exclude the files in specific directories from analysis by adding a `paths-ignore` array.
+For the interpreted languages that {% data variables.product.prodname_codeql %} supports (Python, Ruby, and JavaScript/TypeScript), you can restrict {% data variables.product.prodname_code_scanning %} to files in specific directories by adding a `paths` array to the configuration file. You can exclude the files in specific directories from analysis by adding a `paths-ignore` array.
``` yaml{:copy}
paths:
diff --git a/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md b/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md
index cd81a42915..6c6ad4c90b 100644
--- a/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md
+++ b/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md
@@ -39,8 +39,6 @@ allowTitleToDifferFromFilename: true
To produce more detailed logging output, you can enable step debug logging. For more information, see "[AUTOTITLE](/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging#enabling-step-debug-logging)."
-{% ifversion fpt or ghec or ghes or ghae > 3.3 %}
-
## Creating {% data variables.product.prodname_codeql %} debugging artifacts
You can obtain artifacts to help you debug {% data variables.product.prodname_codeql %}.
@@ -48,8 +46,6 @@ The debug artifacts will be uploaded to the workflow run as an artifact named `d
These artifacts will help you debug problems with {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %}. If you contact GitHub support, they might ask for this data.
-{% endif %}
-
{% ifversion codeql-action-debug-logging %}
### Creating {% data variables.product.prodname_codeql %} debugging artifacts by re-running jobs with debug logging enabled
@@ -60,8 +56,6 @@ You need to ensure that you select **Enable debug logging** . This option enable
{% endif %}
-{% ifversion fpt or ghec or ghes or ghae > 3.3 %}
-
### Creating {% data variables.product.prodname_codeql %} debugging artifacts using a workflow flag
You can create {% data variables.product.prodname_codeql %} debugging artifacts by using a flag in your workflow. For this, you need to modify the `init` step of your {% data variables.code-scanning.codeql_workflow %} file and set `debug: true`.
@@ -73,8 +67,6 @@ You can create {% data variables.product.prodname_codeql %} debugging artifacts
debug: true
```
-{% endif %}
-
{% ifversion code-scanning-without-workflow %}
## Results are different than expected
diff --git a/content/code-security/dependabot/working-with-dependabot/automating-dependabot-with-github-actions.md b/content/code-security/dependabot/working-with-dependabot/automating-dependabot-with-github-actions.md
index 600a0c704a..9d1205637e 100644
--- a/content/code-security/dependabot/working-with-dependabot/automating-dependabot-with-github-actions.md
+++ b/content/code-security/dependabot/working-with-dependabot/automating-dependabot-with-github-actions.md
@@ -32,16 +32,12 @@ redirect_from:
{% data variables.product.prodname_dependabot %} is able to trigger {% data variables.product.prodname_actions %} workflows on its pull requests and comments; however, certain events are treated differently.
-{% ifversion fpt or ghec or ghes or ghae > 3.3 %}
For workflows initiated by {% data variables.product.prodname_dependabot %} (`github.actor == 'dependabot[bot]'`) using the `pull_request`, `pull_request_review`, `pull_request_review_comment`, `push`, `create`, `deployment`, and `deployment_status` events, the following restrictions apply:
-{% endif %}
- `GITHUB_TOKEN` has read-only permissions by default.
- Secrets are populated from {% data variables.product.prodname_dependabot %} secrets. {% data variables.product.prodname_actions %} secrets are not available.
-{% ifversion fpt or ghec or ghes or ghae > 3.3 %}
For workflows initiated by {% data variables.product.prodname_dependabot %} (`github.actor == 'dependabot[bot]'`) using the `pull_request_target` event, if the base ref of the pull request was created by {% data variables.product.prodname_dependabot %} (`github.actor == 'dependabot[bot]'`), the `GITHUB_TOKEN` will be read-only and secrets are not available.
-{% endif %}
{% ifversion actions-stable-actor-ids %}These restrictions apply even if the workflow is re-run by a different actor.{% endif %}
@@ -156,7 +152,7 @@ jobs:
# The following properties are now available:
# - steps.metadata.outputs.dependency-names
# - steps.metadata.outputs.dependency-type
- # - steps.metadata.outputs.update-type
+ # - steps.metadata.outputs.update-type
```
{% endraw %}
diff --git a/content/code-security/getting-started/securing-your-repository.md b/content/code-security/getting-started/securing-your-repository.md
index 316b49b22d..5cd2407ced 100644
--- a/content/code-security/getting-started/securing-your-repository.md
+++ b/content/code-security/getting-started/securing-your-repository.md
@@ -32,8 +32,8 @@ The first step to securing a repository is to establish who can see and modify y
From the main page of your repository, click **{% octicon "gear" aria-label="The Settings gear" %} Settings**, then scroll down to the "Danger Zone."
-- To change who can view your repository, click **Change visibility**. For more information, see "[AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility)."{% ifversion fpt or ghec or ghes or ghae > 3.3 %}
-- To change who can access your repository and adjust permissions, click **Manage access**. For more information, see"[AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository)."{% endif %}
+- To change who can view your repository, click **Change visibility**. For more information, see "[AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility)."
+- To change who can access your repository and adjust permissions, click **Manage access**. For more information, see"[AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository)."
## Managing the dependency graph
diff --git a/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md b/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md
index 697dcaec6b..bc789e4766 100644
--- a/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md
+++ b/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md
@@ -25,7 +25,7 @@ shortTitle: Dependency graph
When you push a commit to {% data variables.product.product_name %} that changes or adds a supported manifest or lock file to the default branch, the dependency graph is automatically updated.{% ifversion fpt or ghec %} In addition, the graph is updated when anyone pushes a change to the repository of one of your dependencies.{% endif %} For information on the supported ecosystems and manifest files, see "[Supported package ecosystems](#supported-package-ecosystems)" below.
-{% ifversion dependency-submission-api %}
+{% ifversion dependency-submission-api %}
{% data reusables.dependency-submission.dependency-submission-link %}
{% endif %}
@@ -80,7 +80,7 @@ The recommended formats explicitly define which versions are used for all direct
| Package manager | Languages | Recommended formats | All supported formats |
| --- | --- | --- | ---|
{%- ifversion dependency-graph-rust-support %}
-| Cargo | Rust | `Cargo.lock` | `Cargo.toml`, `Cargo.lock` |
+| Cargo | Rust | `Cargo.lock` | `Cargo.toml`, `Cargo.lock` |
{%- endif %}
| Composer | PHP | `composer.lock` | `composer.json`, `composer.lock` |
| NuGet | .NET languages (C#, F#, VB), C++ | `.csproj`, `.vbproj`, `.nuspec`, `.vcxproj`, `.fsproj` | `.csproj`, `.vbproj`, `.nuspec`, `.vcxproj`, `.fsproj`, `packages.config` |
@@ -94,9 +94,7 @@ The recommended formats explicitly define which versions are used for all direct
{%- ifversion dependency-graph-dart-support %}
| pub | Dart | `pubspec.lock` | `pubspec.yaml`, `pubspec.lock` |
{%- endif %}
-{%- ifversion fpt or ghec or ghes or ghae > 3.3 %}
| Python Poetry | Python | `poetry.lock` | `poetry.lock`, `pyproject.toml` |
-{%- endif %}
| RubyGems | Ruby | `Gemfile.lock` | `Gemfile.lock`, `Gemfile`, `*.gemspec` |
| Yarn | JavaScript | `yarn.lock` | `package.json`, `yarn.lock` |
diff --git a/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md b/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md
index 5b4a94f759..26eeaa5577 100644
--- a/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md
+++ b/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md
@@ -46,7 +46,8 @@ Organizations are shared accounts where groups of people can collaborate across
To use an organization account with {% data variables.product.prodname_ghe_cloud %}, you will first need to create an organization. When prompted to choose a plan, select "Enterprise". For more information, see "[AUTOTITLE](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)."
-Alternatively, if you have an existing organization account that you would like to upgrade, follow the steps in "[AUTOTITLE](/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription#upgrading-your-organizations-subscription)."
+Alternatively, if you have an existing organization account and would like to upgrade to {% data variables.product.prodname_ghe_cloud %} for additional security, compliance, and deployment controls, follow the steps in "[AUTOTITLE](/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription#upgrading-your-organizations-subscription)."
+
#### 3. Setting up and managing billing
When you choose to use an organization account with {% data variables.product.prodname_ghe_cloud %}, you'll first have access to a [30-day trial](/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud). If you don't purchase {% data variables.product.prodname_enterprise %} or {% data variables.product.prodname_team %} before your trial ends, your organization will be downgraded to {% data variables.product.prodname_free_user %} and lose access to any advanced tooling and features that are only included with paid products. For more information, see "[AUTOTITLE](/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud#finishing-your-trial)."
@@ -63,8 +64,8 @@ An enterprise account allows you to centrally manage policy and settings for mul
#### 2. Creating an enterprise account
- {% data variables.product.prodname_ghe_cloud %} customers paying by invoice can create an enterprise account directly through {% data variables.product.prodname_dotcom %}. For more information, see "[AUTOTITLE](/enterprise-cloud@latest/admin/overview/creating-an-enterprise-account)."
-
+ {% data variables.product.prodname_ghe_cloud %} customers paying by invoice can create an enterprise account directly through {% data variables.product.prodname_dotcom %}. For more information, see "[AUTOTITLE](/enterprise-cloud@latest/admin/overview/creating-an-enterprise-account)."
+
{% data variables.product.prodname_ghe_cloud %} customers not currently paying by invoice can contact [{% data variables.product.prodname_dotcom %}'s Sales team](https://enterprise.github.com/contact) to create an enterprise account for you.
#### 3. Adding organizations to your enterprise account
@@ -78,7 +79,7 @@ You can view your current subscription, license usage, invoices, payment history
## Part 3: Managing your organization or enterprise members and teams with {% data variables.product.prodname_ghe_cloud %}
### Managing members and teams in your organization
-You can set permissions and member roles, create and manage teams, and give people access to repositories in your organization.
+You can set permissions and member roles, create and manage teams, and give people access to repositories in your organization.
#### 1. Managing members of your organization
{% data reusables.getting-started.managing-org-members %}
#### 2. Organization permissions and roles
@@ -131,7 +132,7 @@ Organization owners can enable team synchronization between your identity provid
### Managing security for an {% data variables.enterprise.prodname_emu_enterprise %}
-With {% data variables.product.prodname_emus %}, access and identity is managed centrally through your identity provider. Two-factor authentication and other login requirements should be enabled and enforced on your IdP.
+With {% data variables.product.prodname_emus %}, access and identity is managed centrally through your identity provider. Two-factor authentication and other login requirements should be enabled and enforced on your IdP.
#### 1. Enabling and SAML single sign-on and provisioning in your {% data variables.enterprise.prodname_emu_enterprise %}
@@ -149,10 +150,10 @@ You can configure an allow list for specific IP addresses to restrict access to
{% data reusables.getting-started.enterprise-advanced-security %}
### Managing security for an enterprise account without {% data variables.enterprise.prodname_managed_users %}
-To manage security for your enterprise, you can require two-factor authentication, manage allowed IP addresses, enable SAML single sign-on and team synchronization at an enterprise level, and sign up for and enforce GitHub Advanced Security features.
+To manage security for your enterprise, you can require two-factor authentication, manage allowed IP addresses, enable SAML single sign-on and team synchronization at an enterprise level, and sign up for and enforce GitHub Advanced Security features.
#### 1. Requiring two-factor authentication and managing allowed IP addresses for organizations in your enterprise account
-Enterprise owners can require that organization members, billing managers, and outside collaborators in all organizations owned by an enterprise account use two-factor authentication to secure their personal accounts. Before doing so, we recommend notifying all who have access to organizations in your enterprise. You can also configure an allow list for specific IP addresses to restrict access to assets owned by organizations in your enterprise account.
+Enterprise owners can require that organization members, billing managers, and outside collaborators in all organizations owned by an enterprise account use two-factor authentication to secure their personal accounts. Before doing so, we recommend notifying all who have access to organizations in your enterprise. You can also configure an allow list for specific IP addresses to restrict access to assets owned by organizations in your enterprise account.
For more information on enforcing two-factor authentication and allowed IP address lists, see "[AUTOTITLE](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise)."
#### 2. Enabling and enforcing SAML single sign-on for organizations in your enterprise account
@@ -194,13 +195,13 @@ Members of your organization or enterprise can use tools from the {% data variab
{% data reusables.getting-started.api %}
### 3. Building {% data variables.product.prodname_actions %}
{% data reusables.getting-started.actions %}
-### 4. Publishing and managing {% data variables.product.prodname_registry %}
+### 4. Publishing and managing {% data variables.product.prodname_registry %}
{% data reusables.getting-started.packages %}
### 5. Using {% data variables.product.prodname_pages %}
{% data variables.product.prodname_pages %} is a static site hosting service that takes HTML, CSS, and JavaScript files straight from a repository and publishes a website. You can manage the publication of {% data variables.product.prodname_pages %} sites at the organization level. For more information, see "[AUTOTITLE](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)" and "[AUTOTITLE](/pages/getting-started-with-github-pages/about-github-pages)."
## Part 7: Participating in {% data variables.product.prodname_dotcom %}'s community
-Members of your organization or enterprise can use GitHub's learning and support resources to get the help they need. You can also support the open source community.
+Members of your organization or enterprise can use GitHub's learning and support resources to get the help they need. You can also support the open source community.
### 1. Reading about {% data variables.product.prodname_ghe_cloud %} on {% data variables.product.prodname_docs %}
diff --git a/content/get-started/using-github/keyboard-shortcuts.md b/content/get-started/using-github/keyboard-shortcuts.md
index 049efbfd80..2b5150a1ba 100644
--- a/content/get-started/using-github/keyboard-shortcuts.md
+++ b/content/get-started/using-github/keyboard-shortcuts.md
@@ -91,8 +91,8 @@ For more keyboard shortcuts, see the [CodeMirror documentation](https://codemirr
|-----------|------------
|Command+B (Mac) or Ctrl+B (Windows/Linux) | Inserts Markdown formatting for bolding text
|Command+I (Mac) or Ctrl+I (Windows/Linux) | Inserts Markdown formatting for italicizing text
-|Command+E (Mac) or Ctrl+E (Windows/Linux) | Inserts Markdown formatting for code or a command within a line{% ifversion fpt or ghae > 3.3 or ghes or ghec %}
-|Command+K (Mac) or Ctrl+K (Windows/Linux) | Inserts Markdown formatting for creating a link{% endif %}{% ifversion fpt or ghae > 3.5 or ghes > 3.5 or ghec %}
+|Command+E (Mac) or Ctrl+E (Windows/Linux) | Inserts Markdown formatting for code or a command within a line
+|Command+K (Mac) or Ctrl+K (Windows/Linux) | Inserts Markdown formatting for creating a link{% ifversion fpt or ghae > 3.5 or ghes > 3.5 or ghec %}
|Command+V (Mac) or Ctrl+V (Windows/Linux) | Creates a Markdown link when applied over highlighted text{% endif %}
|Command+Shift+P (Mac) or Ctrl+Shift+P (Windows/Linux) | Toggles between the **Write** and **Preview** comment tabs
|Command+Shift+V (Mac) or Ctrl+Shift+V (Windows/Linux) | Pastes HTML link as plain text
diff --git a/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md b/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md
index 445d0e3d3d..8b8fe7d47c 100644
--- a/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md
+++ b/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md
@@ -24,13 +24,13 @@ To create a heading, add one to six # symbols before your heading tex
-When you use two or more headings, GitHub automatically generates a table of contents which you can access by clicking {% octicon "list-unordered" aria-label="The unordered list icon" %} within the file header. Each heading title is listed in the table of contents and you can click a title to navigate to the selected section.
+When you use two or more headings, GitHub automatically generates a table of contents which you can access by clicking {% octicon "list-unordered" aria-label="The unordered list icon" %} within the file header. Each heading title is listed in the table of contents and you can click a title to navigate to the selected section.
## Styling text
-You can indicate emphasis with bold, italic, strikethrough, subscript, or superscript text in comment fields and `.md` files.
+You can indicate emphasis with bold, italic, strikethrough, subscript, or superscript text in comment fields and `.md` files.
| Style | Syntax | Keyboard shortcut | Example | Output |
| --- | --- | --- | --- | --- |
@@ -116,7 +116,7 @@ Here are the currently supported color models.
## Links
-You can create an inline link by wrapping link text in brackets `[ ]`, and then wrapping the URL in parentheses `( )`. You can also use the keyboard shortcut Command+K to create a link.{% ifversion fpt or ghae > 3.3 or ghes or ghec %} When you have text selected, you can paste a URL from your clipboard to automatically create a link from the selection.{% endif %}
+You can create an inline link by wrapping link text in brackets `[ ]`, and then wrapping the URL in parentheses `( )`. You can also use the keyboard shortcut Command+K to create a link. When you have text selected, you can paste a URL from your clipboard to automatically create a link from the selection.
{% ifversion fpt or ghae > 3.5 or ghes > 3.5 or ghec %} You can also create a Markdown hyperlink by highlighting the text and using the keyboard shortcut Command+V. If you'd like to replace the text with the link, use the keyboard shortcut Command+Shift+V.{% endif %}
@@ -172,7 +172,6 @@ Here are some examples for using relative links to display an image.
For more information, see "[Relative Links](#relative-links)."
-{% ifversion fpt or ghec or ghes or ghae > 3.3 %}
### Specifying the theme an image is shown to
You can specify the theme an image is displayed for in Markdown by using the HTML `` element in combination with the `prefers-color-scheme` media feature. We distinguish between light and dark color modes, so there are two options available. You can use these options to display images optimized for dark or light backgrounds. This is particularly helpful for transparent PNG images.
@@ -182,7 +181,6 @@ For example, the following code displays a sun image for light themes and a moon
{% data reusables.getting-started.picture-element-example %}
The old method of specifying images based on the theme, by using a fragment appended to the URL (`#gh-dark-mode-only` or `#gh-light-mode-only`), is deprecated and will be removed in favor of the new method described above.
-{% endif %}
## Lists
@@ -237,7 +235,7 @@ In this example, you could add a nested list item under the list item `100. Firs
- First nested list item
```
-
+
You can create multiple levels of nested lists using the same method. For example, because the first nested list item has seven characters (`␣␣␣␣␣-␣`) before the nested list content `First nested list item`, you would need to indent the second nested list item by seven spaces.
@@ -247,7 +245,7 @@ You can create multiple levels of nested lists using the same method. For exampl
- Second nested list item
```
-
+
For more examples, see the [GitHub Flavored Markdown Spec](https://github.github.com/gfm/#example-265).
@@ -319,15 +317,15 @@ You can add footnotes to your content by using this bracket syntax:
```
Here is a simple footnote[^1].
-A footnote can also have multiple lines[^2].
+A footnote can also have multiple lines[^2].
You can also use words, to fit your writing style more closely[^note].
[^1]: My reference.
-[^2]: Every new line should be prefixed with 2 spaces.
+[^2]: Every new line should be prefixed with 2 spaces.
This allows you to have a footnote with multiple lines.
[^note]:
- Named footnotes will still render with numbers instead of the text but allow easier identification and linking.
+ Named footnotes will still render with numbers instead of the text but allow easier identification and linking.
This footnote also has been made with a different syntax using 4 spaces for new lines.
```
diff --git a/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md b/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md
index e82242ec12..4756ce775c 100644
--- a/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md
+++ b/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md
@@ -903,7 +903,6 @@ For more information, see "[AUTOTITLE](/organizations/managing-organization-sett
{% data reusables.actions.actions-audit-events-workflow %}
## Further reading
-- "[AUTOTITLE](/organizations/keeping-your-organization-secure)"{% ifversion fpt or ghec or ghes or ghae > 3.3 %}
+- "[AUTOTITLE](/organizations/keeping-your-organization-secure)"
{%- ifversion fpt or ghec %}
-- "[AUTOTITLE](/organizations/managing-membership-in-your-organization/exporting-member-information-for-your-organization)"{% endif %}
-{%- endif %}
+- "[AUTOTITLE](/organizations/managing-membership-in-your-organization/exporting-member-information-for-your-organization)"{% endif %}
\ No newline at end of file
diff --git a/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization.md b/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization.md
index eb5551abf5..ce8915a6d2 100644
--- a/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization.md
+++ b/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization.md
@@ -28,7 +28,7 @@ Members of a team with the security manager role have only the permissions requi
Additional functionality, including a security overview for the organization, is available in organizations that use {% data variables.product.prodname_ghe_cloud %} with {% data variables.product.prodname_advanced_security %}. For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization).
{% endif %}
-If a team has the security manager role, people with admin access to the team and a specific repository can change the team's level of access to that repository but cannot remove the access. For more information, see "[AUTOTITLE](/organizations/managing-user-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository){% ifversion fpt or ghec or ghes or ghae > 3.3 %}" and "[AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository)."{% else %}."{% endif %}
+If a team has the security manager role, people with admin access to the team and a specific repository can change the team's level of access to that repository but cannot remove the access. For more information, see "[AUTOTITLE](/organizations/managing-user-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)" and "[AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository)."
@@ -38,7 +38,7 @@ You can assign the security manager role to a maximum of 10 teams in your organi
{% data reusables.profile.access_org %}
{% data reusables.profile.org_settings %}
{% data reusables.organizations.security-and-analysis %}
-1. Under **Security managers**, search for and select the team to give the role. Each team you select will appear in a list below the search bar.
+1. Under **Security managers**, search for and select the team to give the role. Each team you select will appear in a list below the search bar.
## Removing the security manager role from a team in your organization
diff --git a/content/organizations/managing-user-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md b/content/organizations/managing-user-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md
index aa726252c1..c44f561ab9 100644
--- a/content/organizations/managing-user-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md
+++ b/content/organizations/managing-user-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md
@@ -39,15 +39,4 @@ If your organization requires two-factor authentication, all outside collaborato
## Adding outside collaborators to a repository
-{% ifversion fpt or ghec or ghes or ghae > 3.3 %}
-You can give outside collaborators access to a repository in your repository settings. For more information, see "[AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository#inviting-a-team-or-person)."
-{% else %}
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.repositories.sidebar-settings %}
-5. In the left sidebar, click **Collaborators & teams**.
- 
-6. Under "Collaborators", type the name of the person you'd like to give access to the repository, then click **Add collaborator**.
-
-7. Next to the new collaborator's name, use the drop-down menu and select the appropriate access level.
-
-{% endif %}
+You can give outside collaborators access to a repository in your repository settings. For more information, see "[AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository#inviting-a-team-or-person)."
diff --git a/content/organizations/managing-user-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md b/content/organizations/managing-user-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md
index 17129a56b5..48605f0b47 100644
--- a/content/organizations/managing-user-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md
+++ b/content/organizations/managing-user-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md
@@ -25,34 +25,9 @@ When you remove a collaborator from a repository in your organization, the colla
{% data reusables.repositories.deleted_forks_from_private_repositories_warning %}
-{% ifversion fpt or ghec or ghes or ghae > 3.3 %}
## Managing an individual's access to an organization repository
You can give a person access to a repository or change a person's level of access to a repository in your repository settings. For more information, see "[AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository)."
-{% else %}
-## Giving a person access to a repository
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.repositories.sidebar-settings %}
-{% data reusables.repositories.navigate-to-manage-access %}
-{% data reusables.organizations.invite-teams-or-people %}
-1. In the search field, start typing the name of the person to invite, then click a name in the list of matches.
- 
-6. Under "Choose a role", select the repository role to assign the person, then click **Add NAME to REPOSITORY**.
- 
-
-## Managing an individual's access to an organization repository
-
-{% data reusables.profile.access_org %}
-{% data reusables.user-settings.access_org %}
-{% data reusables.organizations.people %}
-4. Click either **Members** or **Outside collaborators** to manage people with different types of access. 
-5. To the right of the name of the person you'd like to manage, use the {% octicon "gear" aria-label="The Settings gear" %} drop-down menu, and click **Manage**.
- 
-6. On the "Manage access" page, next to the repository, click **Manage access**.
-
-7. Review the person's access to a given repository, such as whether they're a collaborator or have access to the repository via team membership.
-
-{% endif %}
## Further reading
{% ifversion fpt or ghec %}- "[AUTOTITLE](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)"{% endif %}
diff --git a/content/organizations/managing-user-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository.md b/content/organizations/managing-user-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository.md
index 3e4bef6b2e..4e69e6172e 100644
--- a/content/organizations/managing-user-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository.md
+++ b/content/organizations/managing-user-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository.md
@@ -29,46 +29,16 @@ People with admin access to a repository can manage team access to the repositor
## Giving a team access to a repository
-{% ifversion fpt or ghec or ghes or ghae > 3.3 %}
-You can give a team access to a repository or change a team's level of access to a repository in your repository settings. For more information, see "[AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository#inviting-a-team-or-person)."
-{% else %}
-{% data reusables.profile.access_org %}
-{% data reusables.user-settings.access_org %}
-{% data reusables.organizations.specific_team %}
-{% data reusables.organizations.team-repositories-tab %}
-5. Above the list of repositories, click **Add repository**.
- 
-6. Type the name of a repository, then click **Add repository to team**.
- 
-7. Optionally, to the right of the repository name, use the drop-down menu and choose a different permission level for the team.
- 
-{% endif %}
+You can give a team access to a repository or change a team's level of access to a repository in your repository settings. For more information, see "[AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository#inviting-a-team-or-person)."
+
## Removing a team's access to a repository
-{% ifversion fpt or ghec or ghes or ghae > 3.3 %}
You can remove a team's access to an organization repository in your repository settings. For more information, see "[AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository#removing-access-for-a-team-or-person)."
If a team has direct access to a repository, you can remove that team's access to the repository. If a team's access to the repository is inherited from a parent team, you must remove the repository from the parent team in order to remove the repository from child teams.
{% data reusables.repositories.deleted_forks_from_private_repositories_warning %}
-{% else %}
-
-You can remove a team's access to a repository if the team has direct access to a repository. If a team's access to the repository is inherited from a parent team, you must remove the repository from the parent team in order to remove the repository from child teams.
-
-{% data reusables.repositories.deleted_forks_from_private_repositories_warning %}
-
-{% data reusables.profile.access_org %}
-{% data reusables.user-settings.access_org %}
-{% data reusables.organizations.specific_team %}
-{% data reusables.organizations.team-repositories-tab %}
-5. Select the repository or repositories you'd like to remove from the team.
- 
-6. Above the list of repositories, use the drop-down menu, and click **Remove from team**.
- 
-7. Review the repository or repositories that will be removed from the team, then click **Remove repositories**.
- 
-{% endif %}
## Further reading
- "[AUTOTITLE](/organizations/managing-user-access-to-your-organizations-repositories/repository-roles-for-an-organization)"
diff --git a/content/organizations/managing-user-access-to-your-organizations-repositories/removing-an-outside-collaborator-from-an-organization-repository.md b/content/organizations/managing-user-access-to-your-organizations-repositories/removing-an-outside-collaborator-from-an-organization-repository.md
index c46f0802b9..6bedea14da 100644
--- a/content/organizations/managing-user-access-to-your-organizations-repositories/removing-an-outside-collaborator-from-an-organization-repository.md
+++ b/content/organizations/managing-user-access-to-your-organizations-repositories/removing-an-outside-collaborator-from-an-organization-repository.md
@@ -61,9 +61,8 @@ If you only want to remove an outside collaborator from certain repositories in
8. To confirm, click **Remove access**.
-{% ifversion fpt or ghec or ghes or ghae > 3.3 %}
You can also remove an outside collaborator from a repository in the access overview in your repository settings. For more information, see "[AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository#removing-access-for-a-team-or-person)."
-{% endif %}
+
## Further reading
- "[AUTOTITLE](/organizations/managing-user-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization)"
diff --git a/content/organizations/managing-user-access-to-your-organizations-repositories/viewing-people-with-access-to-your-repository.md b/content/organizations/managing-user-access-to-your-organizations-repositories/viewing-people-with-access-to-your-repository.md
index 0b9897491b..38ad7ac982 100644
--- a/content/organizations/managing-user-access-to-your-organizations-repositories/viewing-people-with-access-to-your-repository.md
+++ b/content/organizations/managing-user-access-to-your-organizations-repositories/viewing-people-with-access-to-your-repository.md
@@ -19,20 +19,17 @@ permissions: Organization owners can view people with access to a repository.
## About the list of people with access to your repository
-You can use this information to help off-board people, gather data for compliance, and other general security checkups.
+You can use this information to help off-board people, gather data for compliance, and other general security checkups.
{% ifversion fpt %}
Organizations that use {% data variables.product.prodname_ghe_cloud %} can also export a CSV list of people who have access to a repository. For more information, see [the {% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/organizations/managing-user-access-to-your-organizations-repositories/viewing-people-with-access-to-your-repository).
{% endif %}
-{% ifversion fpt or ghec or ghes or ghae > 3.3 %}
-{% else %}
-
-{% endif %}
+
## Viewing people with access to your repository
-You can see a combined overview of teams and people with access to your repository in your repository settings. For more information, see "[AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository#about-access-management-for-repositories)."
+You can see a combined overview of teams and people with access to your repository in your repository settings. For more information, see "[AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository#about-access-management-for-repositories)."
{% ifversion ghec or ghes or ghae %}
## Exporting a list of people with access to your repository
diff --git a/content/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team.md b/content/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team.md
index 25760efe72..9b2840237f 100644
--- a/content/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team.md
+++ b/content/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team.md
@@ -83,12 +83,9 @@ Any team members that have set their status to "Busy" will not be selected for r
1. Optionally, to always skip certain members of the team, select **Never assign certain team members**. Then, select one or more team members you'd like to always skip.
-
-{% ifversion fpt or ghec or ghes or ghae > 3.3 %}
1. Optionally, to include members of child teams as potential reviewers when assigning requests, select **Child team members**.
1. Optionally, to count any members whose review has already been requested against the total number of members to assign, select **Count existing requests**.
1. Optionally, to remove the review request from the team when assigning team members, select **Team review request**.
-{%- endif %}
1. Click **Save changes**.
## Disabling auto assignment
diff --git a/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md b/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md
index 0187479362..75d64cbe13 100644
--- a/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md
+++ b/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md
@@ -99,7 +99,7 @@ Before you can enable required status checks, you must configure the repository
After enabling required status checks, all required status checks must pass before collaborators can merge changes into the protected branch. After all required status checks pass, any commits must either be pushed to another branch and then merged or pushed directly to the protected branch.
-Any person or integration with write permissions to a repository can set the state of any status check in the repository{% ifversion fpt or ghes or ghae > 3.3 or ghec %}, but in some cases you may only want to accept a status check from a specific {% data variables.product.prodname_github_app %}. When you add a required status check, you can select an app that has recently set this check as the expected source of status updates.{% endif %} If the status is set by any other person or integration, merging won't be allowed. If you select "any source", you can still manually verify the author of each status, listed in the merge box.
+Any person or integration with write permissions to a repository can set the state of any status check in the repository, but in some cases you may only want to accept a status check from a specific {% data variables.product.prodname_github_app %}. When you add a required status check, you can select an app that has recently set this check as the expected source of status updates. If the status is set by any other person or integration, merging won't be allowed. If you select "any source", you can still manually verify the author of each status, listed in the merge box.
You can set up required status checks to either be "loose" or "strict." The type of required status check you choose determines whether your branch is required to be up to date with the base branch before merging.
@@ -191,7 +191,6 @@ You can only give push access to a protected branch, or give permission to creat
### Allow force pushes
-{% ifversion fpt or ghec or ghes or ghae > 3.3 %}
By default, {% data variables.product.product_name %} blocks force pushes on all protected branches. When you enable force pushes to a protected branch, you can choose one of two groups who can force push:
1. Allow everyone with at least write permissions to the repository to force push to the branch, including those with admin permissions.
@@ -199,10 +198,6 @@ By default, {% data variables.product.product_name %} blocks force pushes on all
If someone force pushes to a branch, the force push may overwrite commits that other collaborators based their work on. People may have merge conflicts or corrupted pull requests.
-{% else %}
-By default, {% data variables.product.product_name %} blocks force pushes on all protected branches. When you enable force pushes to a protected branch, anyone with at least write permissions to the repository can force push to the branch, including those with admin permissions. If someone force pushes to a branch, the force push may overwrite commits that other collaborators based their work on. People may have merge conflicts or corrupted pull requests.
-{% endif %}
-
Enabling force pushes will not override any other branch protection rules. For example, if a branch requires a linear commit history, you cannot force push merge commits to that branch.
{% ifversion ghes or ghae %}You cannot enable force pushes for a protected branch if a site administrator has blocked force pushes to all branches in your repository. For more information, see "[AUTOTITLE](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise)."
diff --git a/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md b/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md
index f21537c5fa..60a3a69a74 100644
--- a/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md
+++ b/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md
@@ -50,27 +50,17 @@ When you create a branch rule, the branch you specify doesn't have to exist yet
{% data reusables.repositories.sidebar-settings %}
{% data reusables.repositories.repository-branches %}
{% data reusables.repositories.add-branch-protection-rules %}
-{% ifversion fpt or ghec or ghes or ghae > 3.3 %}
1. Optionally, enable required pull requests.
- Under "Protect matching branches", select **Require a pull request before merging**.
- Optionally, to require approvals before a pull request can be merged, select **Require approvals**, click the **Required number of approvals before merging** drop-down menu, then select the number of approving reviews you would like to require on the branch.
-{% else %}
-1. Optionally, enable required pull request reviews.
- - Under "Protect matching branches", select **Require pull request reviews before merging**.
- 
- - Click the **Required approving reviews** drop-down menu, then select the number of approving reviews you would like to require on the branch.
- 
-{% endif %}
- Optionally, to dismiss a pull request approval review when a code-modifying commit is pushed to the branch, select **Dismiss stale pull request approvals when new commits are pushed**.
- Optionally, to require review from a code owner when the pull request affects code that has a designated owner, select **Require review from Code Owners**. For more information, see "[AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners)."
-{% ifversion fpt or ghec or ghes or ghae > 3.3 %}
- Optionally, to allow specific actors to push code to the branch without creating pull requests when they're required, select **Allow specified actors to bypass required pull requests**. Then, search for and select the actors who should be allowed to skip creating a pull request.
![Allow specific actors to bypass pull request requirements checkbox]{% ifversion integration-branch-protection-exceptions %}(/assets/images/help/repository/PR-bypass-requirements-with-apps.png){% else %}(/assets/images/help/repository/PR-bypass-requirements.png){% endif %}
-{% endif %}
- Optionally, if the repository is part of an organization, select **Restrict who can dismiss pull request reviews**. Then, search for and select the actors who are allowed to dismiss pull request reviews. For more information, see "[AUTOTITLE](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/dismissing-a-pull-request-review)."
![Restrict who can dismiss pull request reviews checkbox]{% ifversion integration-branch-protection-exceptions %}(/assets/images/help/repository/PR-review-required-dismissals-with-apps.png){% else %}(/assets/images/help/repository/PR-review-required-dismissals.png){% endif %}
{% ifversion last-pusher-require-approval %}
@@ -105,9 +95,9 @@ When you create a branch rule, the branch you specify doesn't have to exist yet
{%- endif %}
{% ifversion lock-branch %}
1. Optionally, select **Lock branch** to make branch read-only.
-
+
- Optionally, to allow fork syncing, select **Allow fork syncing**.
-
+
{%- endif %}
1. Optionally, select {% ifversion bypass-branch-protections %}**Do not allow bypassing the above settings**.
{% else %}**Apply the rules above to administrators**.
@@ -121,12 +111,10 @@ When you create a branch rule, the branch you specify doesn't have to exist yet
![Branch restriction search]{% ifversion restrict-pushes-create-branch %}(/assets/images/help/repository/restrict-branch-search-with-create.png){% else %}(/assets/images/help/repository/restrict-branch-search.png){% endif %}
1. Optionally, under "Rules applied to everyone including administrators", select **Allow force pushes**.
-{% ifversion fpt or ghec or ghes or ghae > 3.3 %}
Then, choose who can force push to the branch.
- Select **Everyone** to allow everyone with at least write permissions to the repository to force push to the branch, including those with admin permissions.
- Select **Specify who can force push** to allow only specific actors to force push to the branch. Then, search for and select those actors.
![Screenshot of the options to specify who can force push]{% ifversion integration-branch-protection-exceptions %}(/assets/images/help/repository/allow-force-pushes-specify-who-with-apps.png){% else %}(/assets/images/help/repository/allow-force-pushes-specify-who.png){% endif %}
-{% endif %}
For more information about force pushes, see "[AUTOTITLE](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#allow-force-pushes)."
1. Optionally, select **Allow deletions**.
diff --git a/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks.md b/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks.md
index 4763fb6e01..3ea205a450 100644
--- a/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks.md
+++ b/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks.md
@@ -111,7 +111,6 @@ Now the checks will always pass whenever someone sends a pull request that doesn
{% endnote %}
-{% ifversion fpt or ghes or ghae > 3.3 or ghec %}
## Required status checks from unexpected sources
It's also possible for a protected branch to require a status check from a specific {% data variables.product.prodname_github_app %}. If you see a message similar to the following, then you should verify that the check listed in the merge box was set by the expected app.
@@ -119,4 +118,3 @@ It's also possible for a protected branch to require a status check from a speci
```
Required status check "build" was not set by the expected {% data variables.product.prodname_github_app %}.
```
-{% endif %}
diff --git a/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md b/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md
index a358aef12d..e68ce255b8 100644
--- a/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md
+++ b/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md
@@ -138,7 +138,7 @@ By default, when you create a new repository in your personal account, workflows
1. Click **Save** to apply the settings.
{% endif %}
-{% ifversion ghes or ghae > 3.3 or ghec %}
+{% ifversion ghes or ghae or ghec %}
## Allowing access to components in an internal repository
{% ifversion internal-actions %}Actions and reusable workflows in your internal repositories can be shared with internal and private repositories in the same organization or enterprise.{% else %}Members of your enterprise can use internal repositories to work on projects without sharing information publicly.{% endif %} For information about internal repositories, see "[AUTOTITLE](/repositories/creating-and-managing-repositories/about-repositories#about-internal-repositories)."
diff --git a/content/repositories/releasing-projects-on-github/about-releases.md b/content/repositories/releasing-projects-on-github/about-releases.md
index 84670e28ef..addad9923a 100644
--- a/content/repositories/releasing-projects-on-github/about-releases.md
+++ b/content/repositories/releasing-projects-on-github/about-releases.md
@@ -27,9 +27,7 @@ You can receive notifications when new releases are published in a repository wi
Anyone with read access to a repository can view and compare releases, but only people with write permissions to a repository can manage releases. For more information, see "[AUTOTITLE](/repositories/releasing-projects-on-github/managing-releases-in-a-repository)."
-{% ifversion fpt or ghec or ghes or ghae > 3.3 %}
You can manually create release notes while managing a release. Alternatively, you can automatically generate release notes from a default template, or customize your own release notes template. For more information, see "[AUTOTITLE](/repositories/releasing-projects-on-github/automatically-generated-release-notes)."
-{% endif %}
{% ifversion fpt or ghec or ghes > 3.5 or ghae > 3.6 %}
When viewing the details for a release, the creation date for each release asset is shown next to the release asset.
diff --git a/content/repositories/releasing-projects-on-github/comparing-releases.md b/content/repositories/releasing-projects-on-github/comparing-releases.md
index 004de40d7e..dfb927a771 100644
--- a/content/repositories/releasing-projects-on-github/comparing-releases.md
+++ b/content/repositories/releasing-projects-on-github/comparing-releases.md
@@ -15,6 +15,7 @@ redirect_from:
---
{% data reusables.repositories.navigate-to-repo %}
{% data reusables.repositories.releases %}
+
1. Next to the release you want to use as your base, select the **Compare** dropdown menu, then click the tag you want to compare.
diff --git a/content/repositories/releasing-projects-on-github/linking-to-releases.md b/content/repositories/releasing-projects-on-github/linking-to-releases.md
index ee0780c3ac..36e70fe06c 100644
--- a/content/repositories/releasing-projects-on-github/linking-to-releases.md
+++ b/content/repositories/releasing-projects-on-github/linking-to-releases.md
@@ -24,4 +24,4 @@ To link directly to a download of your latest release asset that was manually up
{% data reusables.repositories.navigate-to-repo %}
{% data reusables.repositories.releases %}
-3. To copy a unique URL to your clipboard, find the release you want to link to, right click the title, and copy the URL.
\ No newline at end of file
+1. To copy a unique URL to your clipboard, find the release you want to link to, right click the title, and copy the URL.
diff --git a/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md b/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md
index ae81c949a1..d0e57b7155 100644
--- a/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md
+++ b/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md
@@ -40,9 +40,7 @@ You can choose whether {% data variables.large_files.product_name_long %} ({% da
{% data reusables.releases.previous-release-tag %}
{% data reusables.releases.release-title %}
1. In the "Describe this release" field, type a description for your release.
- {%- ifversion fpt or ghec or ghes or ghae > 3.3 %}
If you @mention anyone in the description, the published release will include a **Contributors** section with an avatar list of all the mentioned users.
- {%- endif %}
{% ifversion fpt or ghec or ghes %} Alternatively, you can automatically generate your release notes by clicking {% ifversion previous-release-tag %}**Generate release notes**{% else %}**Auto-generate release notes**{% endif %}.{% endif %}
{% data reusables.releases.finish-release %}
@@ -63,9 +61,8 @@ You can choose whether {% data variables.large_files.product_name_long %} ({% da
```shell
gh release create v1.3.2 --title "v1.3.2 (beta)" --notes "this is a beta release" --prerelease
```
-{% ifversion fpt or ghes or ghae > 3.3 or ghec %}
+
If you @mention any {% data variables.product.product_name %} users in the notes, the published release on {% data variables.product.prodname_dotcom_the_website %} will include a **Contributors** section with an avatar list of all the mentioned users.
-{% endif %}
{% endcli %}
@@ -76,11 +73,7 @@ If you @mention any {% data variables.product.product_name %} users in the notes
{% data reusables.repositories.navigate-to-repo %}
{% data reusables.repositories.releases %}
{% data reusables.releases.edit-release %}
-4. Edit the details for the release in the form, then click **Update release**.
-
- {%- ifversion fpt or ghec or ghes or ghae > 3.3 %}
- If you add or remove any @mentions of GitHub users in the description, those users will be added or removed from the avatar list in the **Contributors** section of the release.
- {%- endif %}
+4. Edit the details for the release in the form, then click **Update release**. If you add or remove any @mentions of GitHub users in the description, those users will be added or removed from the avatar list in the **Contributors** section of the release.
{% endwebui %}
@@ -96,14 +89,9 @@ Releases cannot currently be edited with {% data variables.product.prodname_cli
{% data reusables.repositories.navigate-to-repo %}
{% data reusables.repositories.releases %}
-{% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.3 %}
3. On the right side of the page, next to the release you want to delete, click {% octicon "trash" aria-label="Delete" %}.
-{% else %}
-3. Click the name of the release you wish to delete.
-4. In the upper-right corner of the page, click **Delete**.
-{% endif %}
5. Click **Delete this release**.
{% endwebui %}
diff --git a/data/reusables/actions/changing-the-access-policy-of-a-runner-group.md b/data/reusables/actions/changing-the-access-policy-of-a-runner-group.md
index 6dfd895ab5..2954f9cf1c 100644
--- a/data/reusables/actions/changing-the-access-policy-of-a-runner-group.md
+++ b/data/reusables/actions/changing-the-access-policy-of-a-runner-group.md
@@ -1,28 +1,25 @@
-{% comment %}
+{% comment %}
Always include a security admonition above this procedure. This is either one of the following, depending on whether the context is self-hosted runners or larger runners.
{% data reusables.actions.self-hosted-runner-security-admonition %}
{% data reusables.actions.hosted-runner-security-admonition %}
-
+
{% endcomment %}
For runner groups in an enterprise, you can change what organizations in the enterprise can access a runner group{% ifversion restrict-groups-to-workflows %} or restrict what workflows a runner group can run{% endif %}. For runner groups in an organization, you can change what repositories in the organization can access a runner group{% ifversion restrict-groups-to-workflows %} or restrict what workflows a runner group can run{% endif %}.
### Changing what organizations or repositories can access a runner group
-{% ifversion fpt or ghec or ghes or ghae > 3.3 %}
{% data reusables.actions.runner-groups-navigate-to-repo-org-enterprise %}
{% data reusables.actions.settings-sidebar-actions-runner-groups-selection %}
1. For runner groups in an enterprise, under **Organization access**, modify what organizations can access the runner group. For runner groups in an organization, under **Repository access**, modify what repositories can access the runner group.
-{% elsif ghae < 3.4 %}
{% data reusables.actions.configure-runner-group-access %}
-{% endif %}
{% ifversion restrict-groups-to-workflows %}
### Changing what workflows can access a runner group
-You can configure a runner group to run either selected workflows or all workflows. For example, you might use this setting to protect secrets that are stored on runners or to standardize deployment workflows by restricting a runner group to run only a specific reusable workflow. This setting cannot be overridden if you are configuring an organization's runner group that was shared by an enterprise.
+You can configure a runner group to run either selected workflows or all workflows. For example, you might use this setting to protect secrets that are stored on runners or to standardize deployment workflows by restricting a runner group to run only a specific reusable workflow. This setting cannot be overridden if you are configuring an organization's runner group that was shared by an enterprise.
{% data reusables.actions.runner-groups-navigate-to-repo-org-enterprise %}
{% data reusables.actions.settings-sidebar-actions-runner-groups-selection %}
1. Under **Workflow access**, select the dropdown menu and click **Selected workflows**.
@@ -30,7 +27,7 @@ You can configure a runner group to run either selected workflows or all workflo
1. Enter a comma separated list of the workflows that can access the runner group. Use the full path, including the repository name and owner. Pin the workflow to a branch, tag, or full SHA. For example: `octo-org/octo-repo/.github/workflows/build.yml@v2, octo-org/octo-repo/.github/workflows/deploy.yml@d6dc6c96df4f32fa27b039f2084f576ed2c5c2a5, monalisa/octo-test/.github/workflows/test.yml@main`.
Only jobs directly defined within the selected workflows will have access to the runner group.
-
+
Organization-owned runner groups cannot access workflows from a different organization in the enterprise; instead, you must create an enterprise-owned runner group.
1. Click **Save**.
diff --git a/data/reusables/actions/changing-the-name-of-a-runner-group.md b/data/reusables/actions/changing-the-name-of-a-runner-group.md
index a8b99c4c31..7ae17f3249 100644
--- a/data/reusables/actions/changing-the-name-of-a-runner-group.md
+++ b/data/reusables/actions/changing-the-name-of-a-runner-group.md
@@ -1,9 +1,5 @@
-{% ifversion fpt or ghec or ghes or ghae > 3.3 %}
{% data reusables.actions.runner-groups-navigate-to-repo-org-enterprise %}
{% data reusables.actions.settings-sidebar-actions-runner-groups-selection %}
1. Change the runner group name.
-
-{% elsif ghae < 3.4 %}
{% data reusables.actions.configure-runner-group %}
1. Change the runner group name.
-{% endif %}
diff --git a/data/reusables/actions/create-runner-group.md b/data/reusables/actions/create-runner-group.md
index 2bf157113c..eb9038a2c8 100644
--- a/data/reusables/actions/create-runner-group.md
+++ b/data/reusables/actions/create-runner-group.md
@@ -1 +1 @@
-1. Click **{% ifversion ghec or ghes or ghae > 3.3 %}Create{%- elsif ghae < 3.4 %}Save{% endif %} group** to create the group and apply the policy.
+1. Click **Create group** to create the group and apply the policy.
diff --git a/data/reusables/actions/creating-a-runner-group-for-an-organization.md b/data/reusables/actions/creating-a-runner-group-for-an-organization.md
index 9ab23edd25..fe23678627 100644
--- a/data/reusables/actions/creating-a-runner-group-for-an-organization.md
+++ b/data/reusables/actions/creating-a-runner-group-for-an-organization.md
@@ -13,7 +13,7 @@ Runners are automatically assigned to the default group when created, and can on
When creating a group, you must choose a policy that defines which repositories{% ifversion restrict-groups-to-workflows %} and workflows{% endif %} have access to the runner group.
-{% ifversion ghec or ghes or ghae > 3.3 %}
+{% ifversion ghec or ghes or ghae %}
{% data reusables.organizations.navigate-to-org %}
{% data reusables.organizations.org_settings %}
{% data reusables.organizations.settings-sidebar-actions-runner-groups %}
diff --git a/data/reusables/actions/moving-a-runner-to-a-group.md b/data/reusables/actions/moving-a-runner-to-a-group.md
index 14870b537c..bd25a848cf 100644
--- a/data/reusables/actions/moving-a-runner-to-a-group.md
+++ b/data/reusables/actions/moving-a-runner-to-a-group.md
@@ -1,15 +1,6 @@
If you don't specify a runner group during the registration process, your new runners are automatically assigned to the default group, and can then be moved to another group.
{% data reusables.actions.self-hosted-runner-navigate-to-org-enterprise %}
-{% ifversion ghec or ghes or ghae > 3.3 %}
1. In the "Runners" list, click the runner that you want to configure.
2. Select the **Runner group** drop-down.
3. In "Move runner to group", choose a destination group for the runner.
-{% elsif ghae < 3.4 %}
-1. In the {% ifversion ghes or ghae %}"Runner groups"{% endif %} section of the settings page, locate the current group of the runner you want to move and expand the list of group members.
- 
-2. Select the checkbox next to the self-hosted runner, and then click **Move to group** to see the available destinations.
- 
-3. To move the runner, click on the destination group.
- 
-{% endif %}
diff --git a/data/reusables/actions/reusable-workflow-artifacts.md b/data/reusables/actions/reusable-workflow-artifacts.md
index c1a40c5b6f..90f8d2bf64 100644
--- a/data/reusables/actions/reusable-workflow-artifacts.md
+++ b/data/reusables/actions/reusable-workflow-artifacts.md
@@ -1,3 +1 @@
-{% ifversion fpt or ghes or ghae > 3.3 or ghec %}
All actions and workflows called within a run have write access to that run's artifacts.
-{% endif %}
diff --git a/data/reusables/actions/reusable-workflows.md b/data/reusables/actions/reusable-workflows.md
index 45fb9bbf9e..eac1d7e0e4 100644
--- a/data/reusables/actions/reusable-workflows.md
+++ b/data/reusables/actions/reusable-workflows.md
@@ -1,4 +1 @@
-{% ifversion fpt or ghes or ghae > 3.3 or ghec %}
-
{% ifversion ghes or ghec or ghae %}You can share workflows with your organization, publicly or privately, by calling{% else %} You can call{% endif %} one workflow from within another workflow. This allows you to reuse workflows, avoiding duplication and making your workflows easier to maintain. For more information, see "[AUTOTITLE](/actions/using-workflows/reusing-workflows)."
-{% endif %}
diff --git a/data/reusables/actions/runner-groups-add-to-enterprise-first-steps.md b/data/reusables/actions/runner-groups-add-to-enterprise-first-steps.md
index 52991ae7e0..10cd103b39 100644
--- a/data/reusables/actions/runner-groups-add-to-enterprise-first-steps.md
+++ b/data/reusables/actions/runner-groups-add-to-enterprise-first-steps.md
@@ -1,11 +1,6 @@
{% data reusables.enterprise-accounts.access-enterprise %}
{% data reusables.enterprise-accounts.policies-tab %}
{% data reusables.enterprise-accounts.actions-tab %}
-{%- ifversion ghec or ghes or ghae > 3.3 %}
{% data reusables.enterprise-accounts.actions-runner-groups-tab %}
1. Click **New runner group**.
-{%- elsif ghae %}
-{% data reusables.enterprise-accounts.actions-runners-tab %}
-1. Use the **Add new** drop-down, and select **New group**.
-{%- endif %}
1. Under "Group name", type a name for your runner group.
diff --git a/data/reusables/actions/self-hosted-runner-add-to-enterprise.md b/data/reusables/actions/self-hosted-runner-add-to-enterprise.md
index b9b36dc0d3..8d5da6a1b1 100644
--- a/data/reusables/actions/self-hosted-runner-add-to-enterprise.md
+++ b/data/reusables/actions/self-hosted-runner-add-to-enterprise.md
@@ -1,16 +1,6 @@
-{%- ifversion ghec or ghes or ghae > 3.3 %}
{% data reusables.enterprise-accounts.access-enterprise %}
{% data reusables.enterprise-accounts.policies-tab %}
{% data reusables.enterprise-accounts.actions-tab %}
{% data reusables.enterprise-accounts.actions-runners-tab %}
{% ifversion actions-hosted-runners %}1. Click **New runner**, then click **New self-hosted runner**.{% else %}1. Click **New runner**.{% endif %}
{% data reusables.actions.self-hosted-runner-configure %}
-{%- elsif ghae %}
-To add a self-hosted runner to an enterprise, you must be an enterprise owner.
-{% data reusables.enterprise-accounts.access-enterprise %}
-{% data reusables.enterprise-accounts.policies-tab %}
-{% data reusables.enterprise-accounts.actions-tab %}
-{% data reusables.enterprise-accounts.actions-runners-tab %}
-1. Click **Add new**, then click **New runner**.
-{% data reusables.actions.self-hosted-runner-configure %}
-{%- endif %}
diff --git a/data/reusables/actions/settings-ui/settings-actions-runner-groups.md b/data/reusables/actions/settings-ui/settings-actions-runner-groups.md
index 49d31c52e9..b11801b09a 100644
--- a/data/reusables/actions/settings-ui/settings-actions-runner-groups.md
+++ b/data/reusables/actions/settings-ui/settings-actions-runner-groups.md
@@ -1,5 +1,5 @@
{% comment %}This reusable is only to be used in other repo/org/enterprise setting reusables.{%- endcomment -%}
-1. In the left sidebar, click {% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}{% octicon "play" aria-label="The {% data variables.product.prodname_actions %} icon" %} **Actions**, then click **Runner groups**.{% else %}**Actions**.{% ifversion ghes or ghae > 3.3 %}
+1. In the left sidebar, click {% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}{% octicon "play" aria-label="The {% data variables.product.prodname_actions %} icon" %} **Actions**, then click **Runner groups**.{% else %}**Actions**.{% ifversion ghes or ghae %}
1. In the left sidebar, under "Actions", click **Runner groups**.
{%- elsif ghes or ghae %}
1. In the left sidebar, under "Actions", click **Runners**.{% endif %}{% endif %}
diff --git a/data/reusables/actions/workflow-dispatch-inputs-example.md b/data/reusables/actions/workflow-dispatch-inputs-example.md
index 552042ea3d..d414f1f8cc 100644
--- a/data/reusables/actions/workflow-dispatch-inputs-example.md
+++ b/data/reusables/actions/workflow-dispatch-inputs-example.md
@@ -5,24 +5,24 @@ on:
logLevel:
description: 'Log level'
required: true
- default: 'warning' {% ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
+ default: 'warning'
type: choice
options:
- info
- warning
- - debug {% endif %}
+ - debug
print_tags:
description: 'True to print to STDOUT'
- required: true {% ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
- type: boolean {% endif %}
+ required: true
+ type: boolean
tags:
description: 'Test scenario tags'
- required: true {% ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
+ required: true
type: string
environment:
description: 'Environment to run tests against'
type: environment
- required: true {% endif %}
+ required: true
jobs:
print-tag:
diff --git a/data/reusables/actions/workflow-dispatch-inputs.md b/data/reusables/actions/workflow-dispatch-inputs.md
index 0096580d42..e5ff762fb3 100644
--- a/data/reusables/actions/workflow-dispatch-inputs.md
+++ b/data/reusables/actions/workflow-dispatch-inputs.md
@@ -9,24 +9,24 @@ on:
logLevel:
description: 'Log level'
required: true
- default: 'warning' {% ifversion fpt or ghec or ghes or ghae > 3.3 %}
+ default: 'warning'
type: choice
options:
- info
- warning
- - debug {% endif %}
+ - debug
print_tags:
description: 'True to print to STDOUT'
- required: true {% ifversion fpt or ghec or ghes or ghae > 3.3 %}
- type: boolean {% endif %}
+ required: true
+ type: boolean
tags:
description: 'Test scenario tags'
- required: true {% ifversion fpt or ghec or ghes or ghae > 3.3 %}
+ required: true
type: string
environment:
description: 'Environment to run tests against'
type: environment
- required: true {% endif %}
+ required: true
jobs:
print-tag:
diff --git a/data/reusables/code-scanning/codeql-languages-bullets.md b/data/reusables/code-scanning/codeql-languages-bullets.md
index bc925d8688..1c7d057666 100644
--- a/data/reusables/code-scanning/codeql-languages-bullets.md
+++ b/data/reusables/code-scanning/codeql-languages-bullets.md
@@ -4,8 +4,8 @@
- Go
- Java{% ifversion codeql-kotlin-beta %}/Kotlin{% endif %}
- JavaScript/TypeScript
-- Python{% ifversion fpt or ghes or ghec or ghae > 3.3 %}
-- Ruby{% endif %}
+- Python
+- Ruby
{% note %}
diff --git a/data/reusables/code-scanning/codeql-languages-keywords.md b/data/reusables/code-scanning/codeql-languages-keywords.md
index e9c3d11f86..9b50298396 100644
--- a/data/reusables/code-scanning/codeql-languages-keywords.md
+++ b/data/reusables/code-scanning/codeql-languages-keywords.md
@@ -1 +1 @@
-`cpp`, `csharp`, `go`, `java`, `javascript`,{% ifversion fpt or ghes or ghae > 3.3 %} `python`, and `ruby`{% else %} and `python`{% endif %}
+`cpp`, `csharp`, `go`, `java`, `javascript`, `python`, and `ruby`
\ No newline at end of file
diff --git a/data/reusables/secret-scanning/partner-secret-list-private-repo.md b/data/reusables/secret-scanning/partner-secret-list-private-repo.md
index 260e0047d1..2f8bb1c235 100644
--- a/data/reusables/secret-scanning/partner-secret-list-private-repo.md
+++ b/data/reusables/secret-scanning/partner-secret-list-private-repo.md
@@ -6,20 +6,17 @@ Adobe | Adobe Service Token | adobe_service_token
Adobe | Adobe Short-Lived Access Token | adobe_short_lived_access_token
Adobe | Adobe JSON Web Token | adobe_jwt
Alibaba Cloud | Alibaba Cloud Access Key ID with Alibaba Cloud Access Key Secret| alibaba_cloud_access_key_id alibaba_cloud_access_key_secret
-{%- ifversion fpt or ghec or ghes or ghae > 3.3 %}
-Amazon | Amazon OAuth Client ID with Amazon OAuth Client Secret | amazon_oauth_client_id amazon_oauth_client_secret{% endif %}
+Amazon | Amazon OAuth Client ID with Amazon OAuth Client Secret | amazon_oauth_client_id amazon_oauth_client_secret
Amazon Web Services (AWS) | Amazon AWS Access Key ID with Amazon AWS Secret Access Key | aws_access_key_id aws_secret_access_key
Amazon Web Services (AWS) | Amazon AWS Session Token with Amazon AWS Temporary Access Key ID and Amazon AWS Secret Access Key | aws_session_token aws_temporary_access_key_id aws_secret_access_key
Asana | Asana {% data variables.product.pat_generic_title_case %} | asana_personal_access_token
Atlassian | Atlassian API Token | atlassian_api_token
Atlassian | Atlassian JSON Web Token | atlassian_jwt
Atlassian | Bitbucket Server {% data variables.product.pat_generic_title_case %} | bitbucket_server_personal_access_token
-{%- ifversion fpt or ghec or ghes or ghae > 3.3 %}
-Azure | Azure Active Directory Application Secret | azure_active_directory_application_secret{% endif %}
+Azure | Azure Active Directory Application Secret | azure_active_directory_application_secret
{%- ifversion fpt or ghec or ghes > 3.8 or ghae > 3.8 %}
Azure | Azure Batch Key Identifiable | azure_batch_key_identifiable{% endif %}
-{%- ifversion fpt or ghec or ghes or ghae > 3.3 %}
-Azure | Azure Cache for Redis Access Key | azure_cache_for_redis_access_key{% endif %}
+Azure | Azure Cache for Redis Access Key | azure_cache_for_redis_access_key
{%- ifversion fpt or ghec or ghes > 3.8 or ghae > 3.8 %}
Azure | Azure CosmosDB Key Identifiable | azure_cosmosdb_key_identifiable{% endif %}
Azure | Azure DevOps {% data variables.product.pat_generic_title_case %} | azure_devops_personal_access_token
@@ -84,8 +81,7 @@ GitHub | GitHub OAuth Access Token | github_oauth_access_token
GitHub | GitHub Refresh Token | github_refresh_token
GitHub | GitHub App Installation Access Token | github_app_installation_access_token
GitHub | GitHub SSH Private Key | github_ssh_private_key
-{%- ifversion fpt or ghec or ghes or ghae > 3.3 %}
-GitLab | GitLab Access Token | gitlab_access_token{% endif %}
+GitLab | GitLab Access Token | gitlab_access_token
GoCardless | GoCardless Live Access Token | gocardless_live_access_token
GoCardless | GoCardless Sandbox Access Token | gocardless_sandbox_access_token
Google | Firebase Cloud Messaging Server Key | firebase_cloud_messaging_server_key
@@ -94,12 +90,9 @@ Google | Google API Key | google_api_key
Google | Google Cloud Private Key ID | google_cloud_private_key_id{% endif %}
Google | Google Cloud Storage Service Account Access Key ID with Google Cloud Storage Access Key Secret | google_cloud_storage_service_account_access_key_id google_cloud_storage_access_key_secret
Google | Google Cloud Storage User Access Key ID with Google Cloud Storage Access Key Secret | google_cloud_storage_user_access_key_id google_cloud_storage_access_key_secret
-{%- ifversion fpt or ghec or ghes or ghae > 3.3 %}
-Google | Google OAuth Access Token | google_oauth_access_token{% endif %}
-{%- ifversion fpt or ghec or ghes or ghae > 3.3 %}
-Google | Google OAuth Client ID with Google OAuth Client Secret | google_oauth_client_id google_oauth_client_secret{% endif %}
-{%- ifversion fpt or ghec or ghes or ghae > 3.3 %}
-Google | Google OAuth Refresh Token | google_oauth_refresh_token{% endif %}
+Google | Google OAuth Access Token | google_oauth_access_token
+Google | Google OAuth Client ID with Google OAuth Client Secret | google_oauth_client_id google_oauth_client_secret
+Google | Google OAuth Refresh Token | google_oauth_refresh_token
Grafana | Grafana API Key | grafana_api_key
{%- ifversion fpt or ghec or ghes > 3.7 or ghae > 3.7 %}
Grafana | Grafana Cloud API Key | grafana_cloud_api_key
@@ -136,28 +129,22 @@ LogicMonitor | LogicMonitor Bearer Token | logicmonitor_bearer_token
LogicMonitor | LogicMonitor LMV1 Access Key | logicmonitor_lmv1_access_key{% endif %}
Mailchimp | Mailchimp API Key | mailchimp_api_key
Mailgun | Mailgun API Key | mailgun_api_key
-{%- ifversion fpt or ghec or ghes or ghae > 3.3 %}
-Mapbox | Mapbox Secret Access Token | mapbox_secret_access_token{% endif %}
+Mapbox | Mapbox Secret Access Token | mapbox_secret_access_token
MessageBird | MessageBird API Key | messagebird_api_key
Meta | Facebook Access Token | facebook_access_token
-{%- ifversion fpt or ghec or ghes or ghae > 3.3 %}
-Midtrans | Midtrans Production Server Key | midtrans_production_server_key{% endif %}
-{%- ifversion fpt or ghec or ghes or ghae > 3.3 %}
-Midtrans | Midtrans Sandbox Server Key | midtrans_sandbox_server_key{% endif %}
+Midtrans | Midtrans Production Server Key | midtrans_production_server_key
+Midtrans | Midtrans Sandbox Server Key | midtrans_sandbox_server_key
New Relic | New Relic Personal API Key | new_relic_personal_api_key
New Relic | New Relic REST API Key | new_relic_rest_api_key
New Relic | New Relic Insights Query Key | new_relic_insights_query_key
New Relic | New Relic License Key | new_relic_license_key
-{%- ifversion fpt or ghec or ghes or ghae > 3.3 %}
-Notion | Notion Integration Token | notion_integration_token{% endif %}
-{%- ifversion fpt or ghec or ghes or ghae > 3.3 %}
-Notion | Notion OAuth Client Secret | notion_oauth_client_secret{% endif %}
+Notion | Notion Integration Token | notion_integration_token
+Notion | Notion OAuth Client Secret | notion_oauth_client_secret
npm | npm Access Token | npm_access_token
NuGet | NuGet API Key | nuget_api_key
{%- ifversion fpt or ghec or ghes > 3.9 or ghae > 3.9 %}
Oculus | Oculus Very Tiny Encrypted Session | oculus_very_tiny_encrypted_session{% endif %}
-{%- ifversion fpt or ghec or ghes or ghae > 3.3 %}
-Octopus Deploy | Octopus Deploy API Key | octopus_deploy_api_key{% endif %}
+Octopus Deploy | Octopus Deploy API Key | octopus_deploy_api_key
Onfido | Onfido Live API Token | onfido_live_api_token
Onfido | Onfido Sandbox API Token | onfido_sandbox_api_token
OpenAI | OpenAI API Key | openai_api_key
@@ -209,12 +196,9 @@ Shopify | Shopify Private App Password | shopify_private_app_password
Slack | Slack API Token | slack_api_token
Slack | Slack Incoming Webhook URL | slack_incoming_webhook_url
Slack | Slack Workflow Webhook URL | slack_workflow_webhook_url
-{%- ifversion fpt or ghec or ghes or ghae > 3.3 %}
-Square | Square Access Token | square_access_token{% endif %}
-{%- ifversion fpt or ghec or ghes or ghae > 3.3 %}
-Square | Square Production Application Secret | square_production_application_secret{% endif %}
-{%- ifversion fpt or ghec or ghes or ghae > 3.3 %}
-Square | Square Sandbox Application Secret | square_sandbox_application_secret{% endif %}
+Square | Square Access Token | square_access_token
+Square | Square Production Application Secret | square_production_application_secret
+Square | Square Sandbox Application Secret | square_sandbox_application_secret
SSLMate | SSLMate API Key | sslmate_api_key
SSLMate | SSLMate Cluster Secret | sslmate_cluster_secret
Stripe | Stripe API Key | stripe_api_key
@@ -223,8 +207,7 @@ Stripe | Stripe Test API Secret Key | stripe_test_secret_key
Stripe | Stripe Live API Restricted Key | stripe_live_restricted_key
Stripe | Stripe Test API Restricted Key | stripe_test_restricted_key
Stripe | Stripe Webhook Signing Secret | stripe_webhook_signing_secret
-{%- ifversion fpt or ghec or ghes or ghae > 3.3 %}
-Supabase | Supabase Service Key | supabase_service_key{% endif %}
+Supabase | Supabase Service Key | supabase_service_key
Tableau | Tableau {% data variables.product.pat_generic_title_case %} | tableau_personal_access_token
Telegram | Telegram Bot Token | telegram_bot_token
{%- ifversion fpt or ghec or ghes > 3.7 or ghae > 3.7 %}
@@ -232,12 +215,10 @@ Telnyx | Telnyx API V2 Key | telnyx_api_v2_key{% endif %}
Tencent Cloud | Tencent Cloud Secret ID | tencent_cloud_secret_id
{%- ifversion fpt or ghec or ghes > 3.7 or ghae > 3.7 %}
Tencent WeChat | Tencent WeChat API App ID | tencent_wechat_api_app_id{% endif %}
-{%- ifversion fpt or ghec or ghes or ghae > 3.3 %}
-Twilio | Twilio Access Token | twilio_access_token{% endif %}
+Twilio | Twilio Access Token | twilio_access_token
Twilio | Twilio Account String Identifier | twilio_account_sid
Twilio | Twilio API Key | twilio_api_key
-{%- ifversion fpt or ghec or ghes or ghae > 3.3 %}
-Typeform | Typeform {% data variables.product.pat_generic_title_case %} | typeform_personal_access_token{% endif %}
+Typeform | Typeform {% data variables.product.pat_generic_title_case %} | typeform_personal_access_token
{%- ifversion fpt or ghec or ghes > 3.6 or ghae > 3.6 %}
Uniwise | WISEflow API Key | wiseflow_api_key{% endif %}
{%- ifversion fpt or ghec or ghes > 3.9 or ghae > 3.9 %}
@@ -248,19 +229,13 @@ WakaTime | WakaTime OAuth Refresh Token | wakatime_oauth_refresh_token{% endif %
WorkOS | WorkOS Production API Key | workos_production_api_key{% endif %}
{%- ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}
WorkOS | WorkOS Staging API Key | workos_staging_api_key{% endif %}
-{%- ifversion fpt or ghec or ghes or ghae > 3.3 %}
-Yandex | Yandex.Cloud API Key | yandex_cloud_api_key{% endif %}
-{%- ifversion fpt or ghec or ghes or ghae > 3.3 %}
-Yandex | Yandex.Cloud IAM Cookie | yandex_cloud_iam_cookie{% endif %}
-{%- ifversion fpt or ghec or ghes or ghae > 3.3 %}
-Yandex | Yandex.Cloud IAM Token | yandex_cloud_iam_token{% endif %}
-{%- ifversion fpt or ghec or ghes or ghae > 3.3 %}
-Yandex | Yandex.Dictionary API Key | yandex_dictionary_api_key{% endif %}
+Yandex | Yandex.Cloud API Key | yandex_cloud_api_key
+Yandex | Yandex.Cloud IAM Cookie | yandex_cloud_iam_cookie
+Yandex | Yandex.Cloud IAM Token | yandex_cloud_iam_token
+Yandex | Yandex.Dictionary API Key | yandex_dictionary_api_key
{%- ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}
Yandex | Yandex.Cloud Access Secret | yandex_iam_access_secret{% endif %}
-{%- ifversion fpt or ghec or ghes or ghae > 3.3 %}
-Yandex | Yandex.Predictor API Key | yandex_predictor_api_key{% endif %}
-{%- ifversion fpt or ghec or ghes or ghae > 3.3 %}
-Yandex | Yandex.Translate API Key | yandex_translate_api_key{% endif %}
+Yandex | Yandex.Predictor API Key | yandex_predictor_api_key
+Yandex | Yandex.Translate API Key | yandex_translate_api_key
{%- ifversion fpt or ghec or ghes > 3.6 or ghae > 3.6 %}
Zuplo | Zuplo Consumer API Key | zuplo_consumer_api_key{% endif %}