Hack week 2025: remove unneeded FBV instances (23) (#54018)

mchammer01 · web-flow · commit 392b52aa918d · 2025-01-21T08:08:41.000Z
diff --git a/content/actions/hosting-your-own-runners/managing-self-hosted-runners/using-labels-with-self-hosted-runners.md b/content/actions/hosting-your-own-runners/managing-self-hosted-runners/using-labels-with-self-hosted-runners.md
@@ -13,7 +13,7 @@ shortTitle: Label runners
 
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-For information on how to use labels to route jobs to specific types of self-hosted runners, see [AUTOTITLE](/actions/hosting-your-own-runners/managing-self-hosted-runners/using-self-hosted-runners-in-a-workflow). {% ifversion target-runner-groups %}You can also route jobs to runners in a specific group. For more information, see [AUTOTITLE](/actions/using-jobs/choosing-the-runner-for-a-job#targeting-runners-in-a-group).{% endif %}
+For information on how to use labels to route jobs to specific types of self-hosted runners, see [AUTOTITLE](/actions/hosting-your-own-runners/managing-self-hosted-runners/using-self-hosted-runners-in-a-workflow). You can also route jobs to runners in a specific group. For more information, see [AUTOTITLE](/actions/using-jobs/choosing-the-runner-for-a-job#targeting-runners-in-a-group).
 
 {% data reusables.actions.self-hosted-runner-management-permissions-required %}
 
diff --git a/content/actions/hosting-your-own-runners/managing-self-hosted-runners/using-self-hosted-runners-in-a-workflow.md b/content/actions/hosting-your-own-runners/managing-self-hosted-runners/using-self-hosted-runners-in-a-workflow.md
@@ -1,6 +1,6 @@
 ---
 title: Using self-hosted runners in a workflow
-intro: 'To use self-hosted runners in a workflow, you can use labels{% ifversion target-runner-groups %} or groups{% endif %} to specify the runner for a job.'
+intro: 'To use self-hosted runners in a workflow, you can use labels or groups to specify the runner for a job.'
 redirect_from:
   - /github/automating-your-workflow-with-github-actions/using-self-hosted-runners-in-a-workflow
   - /actions/automating-your-workflow-with-github-actions/using-self-hosted-runners-in-a-workflow
@@ -15,7 +15,7 @@ shortTitle: Use runners in a workflow
 
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-You can target self-hosted runners for use in a workflow based on the labels assigned to the runners{% ifversion target-runner-groups %}, or their group membership, or a combination of these{% endif %}.
+You can target self-hosted runners for use in a workflow based on the labels assigned to the runners, or their group membership, or a combination of these.
 
 >[!IMPORTANT]Runner Scale Sets do not support multiple labels, only the name of the runner can be used in place of a label. See [AUTOTITLE](/actions/hosting-your-own-runners/managing-self-hosted-runners-with-actions-runner-controller/deploying-runner-scale-sets-with-actions-runner-controller).
 
@@ -27,8 +27,6 @@ Labels allow you to send workflow jobs to specific types of self-hosted runners,
 
 For information on creating custom and default labels, see [AUTOTITLE](/actions/hosting-your-own-runners/managing-self-hosted-runners/using-labels-with-self-hosted-runners).
 
-{% ifversion target-runner-groups %}
-
 ## About self-hosted runner groups
 
 For self-hosted runners defined at the organization {% ifversion ghec or ghes %}or enterprise levels{% else %}level{% endif %}, you can group your runners with shared characteristics into a single runner group and then configure your job to target the runner group.
@@ -37,8 +35,6 @@ To specify a self-hosted runner group for your job, configure `runs-on.group` in
 
 For information on creating and managing runner groups, see [AUTOTITLE](/actions/hosting-your-own-runners/managing-self-hosted-runners/managing-access-to-self-hosted-runners-using-groups).
 
-{% endif %}
-
 {% ifversion repository-actions-runners %}
 
 ## Viewing available runners for a repository
@@ -95,8 +91,6 @@ runs-on: [self-hosted, linux, x64, gpu]
 
 These labels operate cumulatively, so a self-hosted runner must have all four labels to be eligible to process the job.
 
-{% ifversion target-runner-groups %}
-
 ## Using groups to route jobs
 
 {% data reusables.actions.jobs.example-runs-on-groups %}
@@ -105,13 +99,11 @@ These labels operate cumulatively, so a self-hosted runner must have all four la
 
 {% data reusables.actions.jobs.example-runs-on-labels-and-groups %}
 
-{% endif %}
-
 ## Routing precedence for self-hosted runners
 
-When routing a job to a self-hosted runner, {% data variables.product.prodname_dotcom %} looks for a runner that matches the job's `runs-on` labels{% ifversion target-runner-groups %} and groups{% endif %}:
+When routing a job to a self-hosted runner, {% data variables.product.prodname_dotcom %} looks for a runner that matches the job's `runs-on` labels and groups:
 
-* If {% data variables.product.prodname_dotcom %} finds an online and idle runner that matches the job's `runs-on` labels{% ifversion target-runner-groups %} and groups{% endif %}, the job is then assigned and sent to the runner.
+* If {% data variables.product.prodname_dotcom %} finds an online and idle runner that matches the job's `runs-on` labels and groups, the job is then assigned and sent to the runner.
   * If the runner doesn't pick up the assigned job within 60 seconds, the job is re-queued so that a new runner can accept it.
-* If {% data variables.product.prodname_dotcom %} doesn't find an online and idle runner that matches the job's `runs-on` labels {% ifversion target-runner-groups %} and groups{% endif %}, then the job will remain queued until a runner comes online.
+* If {% data variables.product.prodname_dotcom %} doesn't find an online and idle runner that matches the job's `runs-on` labels and groups, then the job will remain queued until a runner comes online.
 * If the job remains queued for more than 24 hours, the job will fail.
diff --git a/content/actions/managing-workflow-runs-and-deployments/managing-workflow-runs/disabling-and-enabling-a-workflow.md b/content/actions/managing-workflow-runs-and-deployments/managing-workflow-runs/disabling-and-enabling-a-workflow.md
@@ -36,15 +36,7 @@ You can also disable and enable a workflow using the REST API. For more informat
 1. In the left sidebar, click the workflow you want to disable.
 1. Click {% octicon "kebab-horizontal" aria-label="Show workflow options" %} to display a dropdown menu and click **Disable workflow**.
 
-   {% ifversion workflow-nav-2022 -%}
    ![Screenshot of a workflow. The "Show workflow options" button, shown with a kebab icon, and the "Disable workflow" menu item are outlined in orange.](/assets/images/help/repository/actions-disable-workflow-2022.png)
-   {%- else -%}
-   ![Screenshot of a workflow. Features apart from the "Disable workflow" menu item are grayed out.](/assets/images/help/repository/actions-disable-workflow.png)
-
-   The disabled workflow is marked {% octicon "stop" aria-label="The stop icon" %} to indicate its status.
-
-   ![Screenshot showing the actions list. The name of the disabled "Greet Everyone" workflow is prefixed with a stop icon.](/assets/images/help/repository/actions-find-disabled-workflow.png)
-   {%- endif %}
 
 {% endwebui %}
 
@@ -70,11 +62,8 @@ You can re-enable a workflow that was previously disabled.
 {% data reusables.repositories.actions-tab %}
 1. In the left sidebar, click the workflow you want to enable.
 
-   {% ifversion workflow-nav-2022 -%}
    ![Screenshot of the "Actions" page. In the left sidebar, a workflow name is highlighted with an outline in dark orange.](/assets/images/help/repository/actions-select-disabled-workflow-2022.png)
-   {%- else -%}
-   ![Screenshot of the "Actions" page. Features are grayed out apart from one workflow name in the left sidebar.](/assets/images/help/repository/actions-select-disabled-workflow.png)
-   {%- endif %}
+
 1. Click **Enable workflow**.
 
 {% endwebui %}
diff --git a/content/actions/managing-workflow-runs-and-deployments/managing-workflow-runs/manually-running-a-workflow.md b/content/actions/managing-workflow-runs-and-deployments/managing-workflow-runs/manually-running-a-workflow.md
@@ -29,11 +29,8 @@ To trigger the `workflow_dispatch` event, your workflow must be in the default b
 {% data reusables.repositories.actions-tab %}
 1. In the left sidebar, click the name of the workflow you want to run.
 
-   {% ifversion workflow-nav-2022 -%}
    ![Screenshot of the "Actions" page. In the left sidebar, a workflow name is highlighted with an outline in dark orange.](/assets/images/help/repository/actions-select-workflow-2022.png)
-   {%- else -%}
-   ![Screenshot of the "Actions" page. Features apart from one workflow in the left sidebar are grayed out.](/assets/images/help/repository/actions-select-workflow.png)
-   {%- endif %}
+
 1. Above the list of workflow runs, click the **Run workflow** button.
 
    > [!NOTE]
diff --git a/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise.md b/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise.md
@@ -42,8 +42,8 @@ In addition to viewing your audit log, you can monitor activity in your enterpri
 
 As an enterprise owner{% ifversion ghes %} or site administrator{% endif %}, you can interact with the audit log data for your enterprise in several ways:
 * You can view the audit log for your enterprise. For more information, see [AUTOTITLE](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing-the-audit-log-for-your-enterprise).
-* You can search the audit log for specific events{% ifversion ghec %} and export audit log data{% endif %}. For more information, see [AUTOTITLE](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/searching-the-audit-log-for-your-enterprise){% ifversion ghec %} and [AUTOTITLE](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/exporting-audit-log-activity-for-your-enterprise){% endif %}.{% ifversion token-audit-log %}
-* You can identify all events that were performed by a specific access token. For more information, see [AUTOTITLE](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/identifying-audit-log-events-performed-by-an-access-token).{% endif %}{% ifversion ghes %}
+* You can search the audit log for specific events{% ifversion ghec %} and export audit log data{% endif %}. For more information, see [AUTOTITLE](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/searching-the-audit-log-for-your-enterprise){% ifversion ghec %} and [AUTOTITLE](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/exporting-audit-log-activity-for-your-enterprise){% endif %}.
+* You can identify all events that were performed by a specific access token. For more information, see [AUTOTITLE](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/identifying-audit-log-events-performed-by-an-access-token).{% ifversion ghes %}
 * You can configure settings, such as the retention period for audit log events and whether Git events are included. For more information, see [AUTOTITLE](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/configuring-the-audit-log-for-your-enterprise).{% endif %}
 {%- ifversion enterprise-audit-log-ip-addresses %}
 * You can display the IP address associated with events in the audit log. For more information, see [AUTOTITLE](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/displaying-ip-addresses-in-the-audit-log-for-your-enterprise).
diff --git a/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/identifying-audit-log-events-performed-by-an-access-token.md b/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/identifying-audit-log-events-performed-by-an-access-token.md
@@ -3,7 +3,8 @@ title: Identifying audit log events performed by an access token
 shortTitle: Identify events by token
 intro: 'You can identify the actions performed by a specific token in your enterprise.'
 versions:
-  feature: token-audit-log
+  ghes: '*'
+  ghec: '*'
 topics:
   - Organizations
   - Authentication
diff --git a/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/searching-the-audit-log-for-your-enterprise.md b/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/searching-the-audit-log-for-your-enterprise.md
@@ -73,9 +73,7 @@ The `key:value` pairs that can be used in a search query are:
 | {% ifversion ghes %} |
 | `business_id` | ID of the enterprise affected by the action (if applicable). |
 | {% endif %} |
-| {% ifversion token-audit-log %} |
 | `created` | Time at which the action occurred.{% ifversion ghes %} If querying the audit log from the site admin dashboard, use `created_at` instead. |
-| {% endif %} |
 | `country`           | Name of the country where the actor was when performing the action. |
 | `country_code`      | Two-letter short code of the country where the actor was when performing the action. |
 | {% ifversion ghes %} |
@@ -162,9 +160,6 @@ Using the qualifier `country`, you can filter events in the audit log based on t
 * `country:Mexico` finds all events that occurred in Mexico.
 * `country:"United States"` all finds events that occurred in the United States.
 
-{% ifversion token-audit-log %}
-
 ### Search based on the token that performed the action
 
 Use the `hashed_token` qualifier to search based on the token that performed the action. Before you can search for a token, you must generate a SHA-256 hash. For more information, see [AUTOTITLE](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/identifying-audit-log-events-performed-by-an-access-token).
-{% endif %}
diff --git a/content/organizations/collaborating-with-your-team/about-team-discussions.md b/content/organizations/collaborating-with-your-team/about-team-discussions.md
@@ -10,9 +10,8 @@ versions:
 topics:
   - Community
 ---
-{% ifversion team-discussions-migration %}
+
 {% data reusables.organizations.team-discussions-migration %}
-{% endif %}
 
 {% data reusables.organizations.team-discussions-purpose %}
 
diff --git a/content/organizations/collaborating-with-your-team/creating-a-team-discussion.md b/content/organizations/collaborating-with-your-team/creating-a-team-discussion.md
@@ -12,9 +12,7 @@ topics:
 shortTitle: Create a team discussion
 ---
 
-{% ifversion team-discussions-migration %}
 {% data reusables.organizations.team-discussions-migration %}
-{% endif %}
 
 {% data reusables.organizations.team-discussions-permissions %} For more information, see [AUTOTITLE](/organizations/collaborating-with-your-team/about-team-discussions).
 
diff --git a/content/organizations/collaborating-with-your-team/editing-or-deleting-a-team-discussion.md b/content/organizations/collaborating-with-your-team/editing-or-deleting-a-team-discussion.md
@@ -12,9 +12,7 @@ topics:
 shortTitle: Manage a team discussion
 ---
 
-{% ifversion team-discussions-migration %}
 {% data reusables.organizations.team-discussions-migration %}
-{% endif %}
 
 {% data reusables.profile.access_org %}
 {% data reusables.user-settings.access_org %}
diff --git a/content/organizations/collaborating-with-your-team/index.md b/content/organizations/collaborating-with-your-team/index.md
@@ -17,6 +17,4 @@ children:
 shortTitle: Collaborate with your team
 ---
 
-{% ifversion team-discussions-migration %}
 {% data reusables.organizations.team-discussions-migration %}
-{% endif %}
diff --git a/content/organizations/collaborating-with-your-team/pinning-a-team-discussion.md b/content/organizations/collaborating-with-your-team/pinning-a-team-discussion.md
@@ -11,9 +11,7 @@ topics:
   - Community
 ---
 
-{% ifversion team-discussions-migration %}
 {% data reusables.organizations.team-discussions-migration %}
-{% endif %}
 
 {% data reusables.profile.access_org %}
 {% data reusables.user-settings.access_org %}
diff --git a/content/organizations/organizing-members-into-teams/about-teams.md b/content/organizations/organizing-members-into-teams/about-teams.md
@@ -17,7 +17,7 @@ topics:
 
 You can use teams to manage access for people in an organization, and for sending notifications. Organization owners and team maintainers can give teams admin, read, or write access to organization repositories. Organization members can send a notification to an entire team by mentioning the team's name. Teams can only be made up of members of your organization, outside collaborators are unable to be on a team.
 
-{% ifversion team-mentions-setting %}Organization owners and team maintainers can disable team notifications. For more information, see [AUTOTITLE](/organizations/organizing-members-into-teams/configuring-team-notifications).{% endif %}
+Organization owners and team maintainers can disable team notifications. For more information, see [AUTOTITLE](/organizations/organizing-members-into-teams/configuring-team-notifications).
 
 Organization members can also send a notification to an entire team by requesting a review from that team. Organization members can request reviews from specific teams with read access to the repository where the pull request is opened. Teams can be designated as owners of certain types or areas of code in a CODEOWNERS file.
 
diff --git a/content/organizations/organizing-members-into-teams/configuring-team-notifications.md b/content/organizations/organizing-members-into-teams/configuring-team-notifications.md
@@ -2,7 +2,9 @@
 title: Configuring team notifications
 intro: 'Team maintainers and organization owners can configure notifications for specific teams.'
 versions:
-  feature: team-mentions-setting
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
 topics:
   - Organizations
   - Teams
diff --git a/content/organizations/organizing-members-into-teams/disabling-team-discussions-for-your-organization.md b/content/organizations/organizing-members-into-teams/disabling-team-discussions-for-your-organization.md
@@ -12,9 +12,7 @@ topics:
 shortTitle: Disable team discussions
 ---
 
-{% ifversion team-discussions-migration %}
 {% data reusables.organizations.team-discussions-migration %}
-{% endif %}
 
 {% data reusables.organizations.team-discussions-default %} For more information on team discussions, see [AUTOTITLE](/organizations/collaborating-with-your-team/about-team-discussions).
 
diff --git a/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md b/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md
@@ -22,19 +22,11 @@ permissions: People with write access for a forked repository can sync the fork
 
 ## Syncing a fork branch from the web UI
 
-{% ifversion syncing-fork-web-ui %}
 1. On {% data variables.product.github %}, navigate to the main page of the forked repository that you want to sync with the upstream repository.
 1. Above the list of files, select the **Sync fork** dropdown menu.
 
     ![Screenshot of the main page of a fork. A dropdown menu, labeled with a sync icon and "Sync fork," is outlined in dark orange.](/assets/images/help/repository/sync-fork-dropdown.png)
 1. Review the details about the commits from the upstream repository, then click **Update branch**.
-{% else %}
-1. On {% data variables.product.github %}, navigate to the main page of the forked repository that you want to sync with the upstream repository.
-1. Above the list of files, select the **Fetch upstream** dropdown menu.
-
-    ![Screenshot of the main page of a fork. A dropdown menu, labeled with a sync icon and "Fetch upstream," is outlined in dark orange.](/assets/images/help/repository/fetch-upstream-drop-down.png)
-1. Review the details about the commits from the upstream repository, then click **Fetch and merge**.
-{% endif %}
 
 If the changes from the upstream repository cause conflicts, {% data variables.product.company_short %} will prompt you to create a pull request to resolve the conflicts.
 
diff --git a/data/reusables/actions/about-runner-groups.md b/data/reusables/actions/about-runner-groups.md
@@ -4,6 +4,4 @@ When you grant access to a runner group, you can see the runner group listed in
 
 When new runners are created, they are automatically assigned to the default group unless otherwise specified. Runners can only be in one group at a time. You can move runners from one runner group to another. For more information, see [Moving a runner to a group](#moving-a-runner-to-a-group).
 
-{% ifversion target-runner-groups %}
 For information on how to route jobs to runners in a specific group, see [AUTOTITLE](/actions/using-jobs/choosing-the-runner-for-a-job#choosing-runners-in-a-group).
-{% endif %}
diff --git a/data/reusables/actions/jobs/choosing-runner-overview.md b/data/reusables/actions/jobs/choosing-runner-overview.md
@@ -2,8 +2,7 @@ Use `jobs.<job_id>.runs-on` to define the type of machine to run the job on.
 
 {% ifversion fpt or ghec %}- The destination machine can be either a [{% data variables.product.prodname_dotcom %}-hosted runner](#choosing-github-hosted-runners), [{% data variables.actions.hosted_runner %}](#choosing-runners-in-a-group), or a [self-hosted runner](#choosing-self-hosted-runners).{% else %}
 * The destination machine can be a [self-hosted runner](#choosing-self-hosted-runners).{% endif %}
-{% ifversion target-runner-groups %}- You can target runners based on the labels assigned to them, or their group membership, or a combination of these.{% else %}
-* You can target runners based on the labels assigned to them.{% endif %}
+* You can target runners based on the labels assigned to them, or their group membership, or a combination of these.
 * You can provide `runs-on` as:
   * A single string
   * A single variable containing a string
diff --git a/data/reusables/actions/section-using-unique-names-for-runner-groups.md b/data/reusables/actions/section-using-unique-names-for-runner-groups.md
@@ -1,5 +1,5 @@
 
-{% ifversion target-runner-groups %}{% ifversion ghec or ghes %}
+{% ifversion ghec or ghes %}
 
 ## Using unique names for runner groups
 
@@ -15,5 +15,3 @@ To avoid ambiguity, a workflow will fail if there are duplicate runner groups in
 {% data reusables.actions.using-prefixes-to-differentiate-runner-groups %}
 
 {% endif %}
-
-{% endif %}
diff --git a/data/reusables/audit_log/audit-log-search-list-info-about-action.md b/data/reusables/audit_log/audit-log-search-list-info-about-action.md
@@ -12,7 +12,7 @@ Each audit log entry shows applicable information about an event, such as:
 {%- ifversion ghec or ghes > 3.12 %}
 * The SAML SSO and SCIM identity of the user (actor) who performed the action
 {%- endif %}
-{%- ifversion token-audit-log %}
+{%- ifversion ghec or ghes %}
 * For actions outside of the web UI, how the user (actor) authenticated
 {%- endif %}
 {%- ifversion enterprise-audit-log-ip-addresses %}
