Merge pull request #35962 from github/repo-sync

Repo sync

content/actions/managing-workflow-runs-and-deployments/managing-workflow-runs/re-running-workflows-and-jobs.md

@@ -16,7 +16,7 @@ versions:
 
 ## About re-running workflows and jobs
 
-Re-running a workflow{% ifversion re-run-jobs %} or jobs in a workflow{% endif %} uses the same `GITHUB_SHA` (commit SHA) and `GITHUB_REF` (Git ref) of the original event that triggered the workflow run. The workflow will use the privileges of the actor who initially triggered the workflow, not the privileges of the actor who initiated the re-run. You can re-run a workflow{% ifversion re-run-jobs %} or jobs in a workflow{% endif %} for up to 30 days after the initial run.{% ifversion re-run-jobs %} You cannot re-run jobs in a workflow once its logs have passed their retention limits. For more information, see [AUTOTITLE](/actions/learn-github-actions/usage-limits-billing-and-administration#artifact-and-log-retention-policy).{% endif %}{% ifversion debug-reruns %} When you re-run a workflow or jobs in a workflow, you can enable debug logging for the re-run. This will enable runner diagnostic logging and step debug logging for the re-run. For more information about debug logging, see [AUTOTITLE](/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging).{% endif %}
+Re-running a workflow{% ifversion re-run-jobs %} or jobs in a workflow{% endif %} uses the same `GITHUB_SHA` (commit SHA) and `GITHUB_REF` (Git ref) of the original event that triggered the workflow run. The workflow will use the privileges of the actor who initially triggered the workflow, not the privileges of the actor who initiated the re-run. You can re-run a workflow{% ifversion re-run-jobs %} or jobs in a workflow{% endif %} for up to 30 days after the initial run.{% ifversion re-run-jobs %} You cannot re-run jobs in a workflow once its logs have passed their retention limits. For more information, see [AUTOTITLE](/actions/learn-github-actions/usage-limits-billing-and-administration#artifact-and-log-retention-policy).{% endif %} When you re-run a workflow or jobs in a workflow, you can enable debug logging for the re-run. This will enable runner diagnostic logging and step debug logging for the re-run. For more information about debug logging, see [AUTOTITLE](/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging).
 
 ## Re-running all the jobs in a workflow
 
@@ -46,15 +46,12 @@ To re-run a failed workflow run, use the `run rerun` subcommand. Replace `run-id
 gh run rerun RUN_ID
 ```
 
-{% ifversion debug-reruns %}
 {% data reusables.actions.enable-debug-logging-cli %}
 
 ```shell
 gh run rerun RUN_ID --debug
 ```
 
-{% endif %}
-
 To view the progress of the workflow run, use the `run watch` subcommand and select the run from the interactive list.
 
 ```shell
@@ -88,14 +85,12 @@ To re-run failed jobs in a workflow run, use the `run rerun` subcommand with the
 gh run rerun RUN_ID --failed
 ```
 
-{% ifversion debug-reruns %}
 {% data reusables.actions.enable-debug-logging-cli %}
 
 ```shell
 gh run rerun RUN_ID --failed --debug
 ```
 
-{% endif %}
 {% endcli %}
 
 ## Re-running a specific job in a workflow
@@ -122,14 +117,12 @@ To re-run a specific job in a workflow run, use the `run rerun` subcommand with
 gh run rerun --job JOB_ID
 ```
 
-{% ifversion debug-reruns %}
 {% data reusables.actions.enable-debug-logging-cli %}
 
 ```shell
 gh run rerun --job JOB_ID --debug
 ```
 
-{% endif %}
 {% endcli %}
 
 {% endif %}

content/actions/monitoring-and-troubleshooting-workflows/troubleshooting-workflows/enabling-debug-logging.md

@@ -21,12 +21,8 @@ These extra logs are enabled by setting secrets or variables in the repository c
 
 For more information on setting secrets and variables, see [AUTOTITLE](/actions/security-guides/using-secrets-in-github-actions) and [AUTOTITLE](/actions/learn-github-actions/variables).
 
-{% ifversion debug-reruns %}
-
 Additionally, anyone who has access to run a workflow can enable runner diagnostic logging and step debug logging for a workflow re-run. For more information, see [AUTOTITLE](/actions/managing-workflow-runs/re-running-workflows-and-jobs).
 
- {% endif %}
-
 ## Enabling runner diagnostic logging
 
 Runner diagnostic logging provides additional log files that contain information about how a runner is executing a job. Two extra log files are added to the log archive:

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

@@ -282,7 +282,7 @@ ghe-org-admin-promote -a
 
 ### ghe-reactivate-admin-login
 
-Use this command to immediately unlock the {% data variables.enterprise.management_console %} after {% ifversion enterprise-authentication-rate-limits %}an account lockout. To configure authentication policies for {% data variables.location.product_location %}, see [AUTOTITLE](/admin/configuration/configuring-your-enterprise/configuring-rate-limits#configuring-authentication-policy-rate-limits).{% else %}10 failed login attempts in the span of 10 minutes.{% endif %}
+Use this command to immediately unlock the {% data variables.enterprise.management_console %} after an account lockout. To configure authentication policies for {% data variables.location.product_location %}, see [AUTOTITLE](/admin/configuration/configuring-your-enterprise/configuring-rate-limits#configuring-authentication-policy-rate-limits).
 
 ```shell
 ghe-reactivate-admin-login
@@ -376,7 +376,7 @@ inactive
 
 ### ghe-set-password
 
-This utility allows you to set a new {% ifversion enterprise-management-console-multi-user-auth %}root site administrator {% endif %}password for authentication to the {% data variables.enterprise.management_console %}. For more information, see [AUTOTITLE](/admin/administering-your-instance/administering-your-instance-from-the-web-ui/managing-access-to-the-management-console).
+This utility allows you to set a new root site administrator password for authentication to the {% data variables.enterprise.management_console %}. For more information, see [AUTOTITLE](/admin/administering-your-instance/administering-your-instance-from-the-web-ui/managing-access-to-the-management-console).
 
 ```shell
 ghe-set-password

content/admin/administering-your-instance/administering-your-instance-from-the-web-ui/about-the-management-console.md

@@ -20,7 +20,7 @@ The {% data variables.enterprise.management_console %} allows you to manage the
 
 You can always reach the {% data variables.enterprise.management_console %} using {% data variables.location.product_location %}'s IP address, even when the instance is in maintenance mode, or there is a critical application failure or hostname or SSL misconfiguration.
 
-To access the {% data variables.enterprise.management_console %}, {% ifversion enterprise-management-console-multi-user-auth %}you can use the root site administrator password established during initial setup of {% data variables.location.product_location %} or log in as a {% data variables.enterprise.management_console %} user. For more information, see [AUTOTITLE](/admin/configuration/administering-your-instance-from-the-management-console/accessing-the-management-console). {% else %}you must use the administrator password established during initial setup of {% data variables.location.product_location %}. {% endif %}You must also be able to connect to the virtual machine host on port 8443. If you're having trouble reaching the {% data variables.enterprise.management_console %}, please check intermediate firewall and security group configurations.
+To access the {% data variables.enterprise.management_console %}, you can use the root site administrator password established during initial setup of {% data variables.location.product_location %} or log in as a {% data variables.enterprise.management_console %} user. For more information, see [AUTOTITLE](/admin/configuration/administering-your-instance-from-the-management-console/accessing-the-management-console). You must also be able to connect to the virtual machine host on port 8443. If you're having trouble reaching the {% data variables.enterprise.management_console %}, please check intermediate firewall and security group configurations.
 
 The {% data variables.enterprise.management_console %} password hash is stored in `/data/user/common/secrets.conf`. If high availability or clustering is configured, the file is automatically synced from the primary node to any additional nodes. Any change to the primary's password will automatically be replicated to all of the instance's nodes. For more information about high availability, see [AUTOTITLE](/admin/enterprise-management/configuring-high-availability/about-high-availability-configuration).
 
@@ -35,10 +35,10 @@ When someone performs an action in the {% data variables.enterprise.management_c
 In the {% data variables.enterprise.management_console %}, you can perform administrative tasks for {% data variables.location.product_location %}, including:
 
 * **Initial setup:** Walk through the initial setup process when first launching {% data variables.location.product_location %} by visiting {% data variables.location.product_location %}'s IP address in your browser.
-{%- ifversion enterprise-management-console-multi-user-auth %}
+
 * **Identity and access management:** Improve the security of {% data variables.location.product_location %} by creating dedicated user accounts for the {% data variables.enterprise.management_console %}. {% ifversion management-console-editor %}The root site administrator account can control these user accounts' access by assigning either the editor or operator role. {% endif %}For more information, see [AUTOTITLE](/admin/configuration/administering-your-instance-from-the-management-console/managing-access-to-the-management-console).{% ifversion management-console-editor %}
   {% data reusables.enterprise.editor-role-note %}{% endif %}
-{%- endif %}
+
 * **Configuring authentication policies for the {% data variables.enterprise.management_console %}:** Set rate limits for login attempts, and the lockout duration if someone exceeds the rate limit. For more information, see [AUTOTITLE](/admin/configuration/administering-your-instance-from-the-management-console/managing-access-to-the-management-console#configuring-rate-limits-for-authentication-to-the-management-console).
 * **Configuring basic settings for your instance:** Configure DNS, hostname, SSL, user authentication, email, monitoring services, and log forwarding on the Settings page.
 * **Scheduling maintenance windows:** Take {% data variables.location.product_location %} offline while performing maintenance using the {% data variables.enterprise.management_console %} or administrative shell.

content/admin/administering-your-instance/administering-your-instance-from-the-web-ui/managing-access-to-the-management-console.md

@@ -1,7 +1,7 @@
 ---
 title: Managing access to the Management Console
 shortTitle: Manage Management Console access
-intro: '{% ifversion enterprise-management-console-multi-user-auth %}You can increase the security of {% data variables.location.product_location %} by creating or deleting {% data variables.enterprise.management_console %} users. As the root site administrator, you {% else %}You {% endif %}can access the {% data variables.enterprise.management_console %} as well as configure {% data variables.enterprise.management_console %} authentication rate limits.'
+intro: 'You can increase the security of {% data variables.location.product_location %} by creating or deleting {% data variables.enterprise.management_console %} users. As the root site administrator, you can access the {% data variables.enterprise.management_console %} as well as configure {% data variables.enterprise.management_console %} authentication rate limits.'
 redirect_from:
   - /admin/configuration/administering-your-instance-from-the-management-console/managing-access-to-the-management-console
 versions:
@@ -18,8 +18,6 @@ topics:
 
 {% ifversion ghes-manage-api-cli-extension %}You can also use the `gh es` {% data variables.product.prodname_cli %} extension to manage the root site administrator password, which controls access to the Management Console. For more information, see the [GH ES CLI usage documentation](https://github.com/github/gh-es/blob/main/USAGE.md#gh-es-access-set-password) and [AUTOTITLE](/admin/administering-your-instance/administering-your-instance-from-the-command-line/administering-your-instance-using-the-github-cli).{% endif %}
 
-{% ifversion enterprise-management-console-multi-user-auth %}
-
 ## Types of {% data variables.enterprise.management_console %} accounts
 
 There are two types of user accounts for the {% data variables.enterprise.management_console %} on a {% data variables.product.product_name %} instance. The root site administrator account authenticates with a password established during the initial setup of {% data variables.location.product_location %}.
@@ -72,10 +70,6 @@ If you have not configured email notifications for {% data variables.location.pr
 1. To copy the invitation link, click {% octicon "link" aria-label="Copy invitation link" %} on any {% data variables.enterprise.management_console %} user account.
 1. Send the invitation link to the {% data variables.enterprise.management_console %} user. The invitation link will lead the user through the final account setup steps.
 
-{% endif %}
-
-{% ifversion enterprise-authentication-rate-limits %}
-
 ## Configuring rate limits for authentication to the {% data variables.enterprise.management_console %}
 
 You can configure the lockout time and login attempt limits for the {% data variables.enterprise.management_console %}.
@@ -87,5 +81,3 @@ After you configure rate limits and a {% data variables.enterprise.management_co
 1. Optionally, under "Lockout time for Management Console users", type a number of minutes to lock the {% data variables.enterprise.management_console %} after too many failed login attempts. When locked out, the root site administrator must be manually unlocked.
 1. Optionally, under "Login attempt limit for all users", type a maximum number of failed login attempts to allow before the {% data variables.enterprise.management_console %} is locked.
 {% data reusables.enterprise_management_console.save-settings %}
-
-{% endif %}

content/admin/administering-your-instance/administering-your-instance-from-the-web-ui/troubleshooting-access-to-the-management-console.md

@@ -20,18 +20,12 @@ If you experience problems accessing the Management Console, you can try the fol
 
 ## Unlocking the {% data variables.enterprise.management_console %} after failed login attempts
 
-The {% data variables.enterprise.management_console %} locks after {% ifversion enterprise-authentication-rate-limits %}the number of failed login attempts configured by your authentication policies. For more information, see [AUTOTITLE](/admin/configuration/administering-your-instance-from-the-management-console/managing-access-to-the-management-console#configuring-rate-limits-for-authentication-to-the-management-console).{% else %}ten failed login attempts are made in the span of ten minutes. You must wait for the login screen to automatically unlock before attempting to log in again. The login screen automatically unlocks as soon as the previous ten minute period contains fewer than ten failed login attempts. The counter resets after a successful login occurs.{% endif %}
+The {% data variables.enterprise.management_console %} locks after the number of failed login attempts configured by your authentication policies. For more information, see [AUTOTITLE](/admin/configuration/administering-your-instance-from-the-management-console/managing-access-to-the-management-console#configuring-rate-limits-for-authentication-to-the-management-console).
-
-{% ifversion enterprise-management-console-multi-user-auth %}
 
 ### Unlocking the root site administrator account
 
-{% endif %}
-
 {% data reusables.enterprise_management_console.unlocking-management-console-with-shell %}
 
-{% ifversion enterprise-management-console-multi-user-auth %}
-
 ### Unlocking a {% data variables.enterprise.management_console %} user account
 
 The root site administrator can unlock access to the {% data variables.enterprise.management_console %} for other user accounts.
@@ -40,8 +34,6 @@ The root site administrator can unlock access to the {% data variables.enterpris
 {% data reusables.enterprise_site_admin_settings.click-user-management %}
 1. Locked user accounts will appear as "State: blocked". To unblock the user and allow authentication, to the right of the user's details, click {% octicon "law" aria-label="Unblock user" %}.
 
-{%- endif %}
-
 ## Troubleshooting failed connections to the {% data variables.enterprise.management_console %}
 
 If you cannot connect to the {% data variables.enterprise.management_console %} on {% data variables.location.product_location %}, you can review the following information to troubleshoot the problem.

content/admin/configuring-packages/migrating-your-enterprise-to-the-container-registry-from-the-docker-registry.md

@@ -4,7 +4,7 @@ intro: 'You can migrate Docker images previously stored in the Docker registry o
 product: '{% data reusables.gated-features.packages %}'
 permissions: 'Enterprise owners can migrate Docker images to the {% data variables.product.prodname_container_registry %}.'
 versions:
-  feature: docker-ghcr-enterprise-migration
+  ghes: '*'
 shortTitle: Migrate to Container registry
 topics:
   - Containers

content/admin/installing-your-enterprise-server/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-azure.md

@@ -77,7 +77,7 @@ Before launching {% data variables.location.product_location %} on Azure, you'll
 
 ## Configuring the {% data variables.product.prodname_ghe_server %} virtual machine
 
-To configure the instance, you must confirm the instance's status, upload a license file, set the {% ifversion enterprise-management-console-multi-user-auth %}root {% endif %} {% data variables.enterprise.management_console %} password, configure the instance's settings, and restart the instance.
+To configure the instance, you must confirm the instance's status, upload a license file, set the root {% data variables.enterprise.management_console %} password, configure the instance's settings, and restart the instance.
 
 {% data reusables.enterprise_installation.new-instance-attack-vector-warning %}
 

content/admin/managing-accounts-and-repositories/communicating-information-to-users-in-your-enterprise/customizing-user-messages-for-your-enterprise.md

@@ -84,21 +84,12 @@ If you include Markdown checkboxes in the message, all checkboxes must be select
 
 Each time a user sees a mandatory message, an audit log event is created. The event includes the version of the message that the user saw. For more information see [AUTOTITLE](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise).
 
-{% ifversion display-mandatory-message-again %} {% else %}
-
-> [!NOTE]
-> If you change the mandatory message for {% data variables.location.product_location %}, users who have already acknowledged the message will not see the new message.
-
-{% endif %}
-
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.messages-tab %}
 1. To the right of "Mandatory message", click **Add mandatory message**.
 1. Under "Mandatory message", in the text box, type your message.
-{%- ifversion display-mandatory-message-again %}
 1. Optionally, select **Show updated message to all users even if they dismissed the previous one**.
-   {% endif %}
 {% data reusables.enterprise_site_admin_settings.message-preview-save %}
 
 {% endif %}

content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise.md

@@ -44,7 +44,7 @@ As an enterprise owner{% ifversion ghes %} or site administrator{% endif %}, you
 * 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 configure settings, such as the retention period for audit log events{% ifversion enable-git-events %} and whether Git events are included{% endif %}. 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 %}
+* 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).
 {%- endif %}

content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/configuring-the-audit-log-for-your-enterprise.md

@@ -16,9 +16,7 @@ topics:
 
 You can configure a retention period for audit log data and see index storage details.
 
-{% ifversion enable-git-events %}
 After you configure a retention period, you can enable or disable Git-related events from appearing in the audit log.
-{% endif %}
 
 ## Configuring a retention period for audit log data
 
@@ -31,15 +29,11 @@ You can configure a retention period for audit log data for {% data variables.lo
 1. Under "Configure audit log retention settings", select the dropdown menu and click a retention period.
 1. Click **Save**.
 
-{% ifversion enable-git-events %}
-
 ## Managing Git events in the audit log
 
 You can enable or disable Git-related events, such as `git.clone` and `git.push`, from appearing in your audit log. For a list of the Git events are logged, see [AUTOTITLE](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise#git).
 
-{% ifversion ghes %}
 If you do enable Git events, due to the large number of Git events that are logged, we recommend monitoring your instance's file storage and reviewing your related alert configurations. For more information, see [AUTOTITLE](/admin/enterprise-management/monitoring-your-appliance/recommended-alert-thresholds#monitoring-storage).
-{% endif %}
 
 Before you can enable Git events in the audit log, you must configure a retention period for audit log data other than "infinite." For more information, see [Configuring a retention period for audit log data](#configuring-a-retention-period-for-audit-log-data).
 
@@ -56,5 +50,3 @@ Before you can enable Git events in the audit log, you must configure a retentio
 
    ![Screenshot of the audit log. The checkbox to enable Git events in the audit log is highlighted with an orange outline.](/assets/images/help/enterprises/enable-git-events-checkbox.png)
 1. Click **Save**.
-
-{% endif %}

content/authentication/keeping-your-account-and-data-secure/viewing-and-managing-your-sessions.md

@@ -2,7 +2,10 @@
 title: Viewing and managing your sessions
 intro: You can view and revoke your active sessions in your settings.
 versions:
-  feature: device-and-settings-management-page
+  fpt: '*'
+  ghec: '*'
+  ghes: '*'
+
 type: how_to
 topics:
   - SSO

content/code-security/code-scanning/troubleshooting-code-scanning/resource-not-accessible.md

@@ -57,7 +57,7 @@ For more information about editing the {% data variables.product.prodname_codeql
 
 If the {% data variables.code-scanning.codeql_workflow %} still fails on a commit made on the default branch, you need to check:
 
-* whether {% data variables.product.prodname_dependabot %} authored the commit
+* Whether {% data variables.product.prodname_dependabot %} authored the commit
-* whether the pull request that includes the commit has been merged using `@dependabot squash and merge`
+* Whether the pull request that includes the commit has been merged using `@dependabot squash and merge`
 
 This type of merge commit is authored by {% data variables.product.prodname_dependabot %} and therefore, any workflows running on the commit will have read-only permissions. If you enabled {% data variables.product.prodname_code_scanning %} and {% data variables.product.prodname_dependabot %} security updates or version updates on your repository, we recommend you avoid using the {% data variables.product.prodname_dependabot %} `@dependabot squash and merge` command. Instead, you can enable auto-merge for your repository. This means that pull requests will be automatically merged when all required reviews are met and status checks have passed. For more information about enabling auto-merge, see [AUTOTITLE](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request#enabling-auto-merge).

content/code-security/code-scanning/troubleshooting-sarif-uploads/file-too-large.md

@@ -40,8 +40,8 @@ There are many potential causes of very large SARIF results files.
 
 Take a look at the results file that was rejected by {% data variables.product.prodname_code_scanning %} to see if:
 
-* the SARIF file was compressed using gzip
+* The SARIF file was compressed using gzip
-* the compressed file is smaller than 10 MB
+* The compressed file is smaller than 10 MB
 
 If the file wasn't compressed using gzip, try compressing the file before rerunning the upload process. If the compressed file is still too large, you need to configure the analysis to generate a smaller set of results.
 

content/code-security/dependabot/working-with-dependabot/dependabot-options-reference.md

@@ -282,7 +282,7 @@ For most package managers, you should define a value that will match the depende
 
 Use to ignore specific versions or ranges of versions. If you want to define a range, use the standard pattern for the package manager. For example:
 
-* npm: use `^1.0.0`
+* npm: use `^1.0.0` <!-- markdownlint-disable-line GHD034 -->
 * Bundler: use `~> 2.0`
 * Docker: use Ruby version syntax
 * NuGet: use `7.*`

content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md

@@ -2,7 +2,9 @@
 title: About discussions
 intro: 'Use discussions to ask and answer questions, share information, make announcements, and conduct or participate in a conversation about a project on {% data variables.product.product_name %}.'
 versions:
-  feature: discussions
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
 ---
 
 
@@ -20,7 +22,7 @@ With {% data variables.product.prodname_discussions %}, the community for your p
 
 You might use repository discussions to discuss topics that are specific to the repository. If your project spans multiple repositories, you might use organization discussions to discuss topics that aren't specific to a single repository in your organization.
 
-{% ifversion discussions-closable %}{% data reusables.discussions.closing-discussions %} For more information, see [Closing a discussion](/discussions/managing-discussions-for-your-community/managing-discussions#closing-a-discussion).{% else %}You don't need to close a discussion like you close an issue or a pull request.{% endif %}
+{% data reusables.discussions.closing-discussions %} For more information, see [Closing a discussion](/discussions/managing-discussions-for-your-community/managing-discussions#closing-a-discussion).
 
 If a repository administrator or project maintainer enables {% data variables.product.prodname_discussions %} for a repository, anyone who has access to the repository can create and participate in discussions for the repository. If an organization owner enables {% data variables.product.prodname_discussions %} for an organization, anyone who can view the source repository can create an organization discussion.
 
@@ -40,7 +42,7 @@ For more information on creating polls, see [AUTOTITLE](/discussions/collaborati
 
 ## About discussion organization
 
-You can organize discussions with categories{% ifversion discussions-category-section %}, sections, {% endif %} and labels.
+You can organize discussions with categories, sections, and labels.
 
 {% data reusables.discussions.you-can-categorize-discussions %} {% data reusables.discussions.about-categories-and-formats %} {% data reusables.discussions.repository-category-limit %}
 
@@ -48,8 +50,7 @@ For discussions with a question/answer format, an individual comment within the
 
 {% data reusables.discussions.about-announcement-format %}
 
-{% ifversion discussions-category-section %}
+{% data reusables.discussions.category-sections %}
-{% data reusables.discussions.category-sections %}{% endif %}
 
 For more information, see [AUTOTITLE](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions).
 

content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md

@@ -4,7 +4,9 @@ shortTitle: Collaborating with maintainers
 intro: 'You can contribute to the goals, plans, health, and community for a project on {% data variables.product.product_name %} by communicating with the maintainers of the project in a discussion.'
 permissions: 'People with read access to a repository can start and participate in discussions and polls in the repository. People with read access to the source repository for organization discussions can start and participate in discussions and polls in the organization. {% data reusables.enterprise-accounts.emu-permission-interact %}'
 versions:
-  feature: discussions
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
 ---
 
 

content/discussions/collaborating-with-your-community-using-discussions/index.md

@@ -3,10 +3,11 @@ title: Collaborating with your community using discussions
 shortTitle: Collaborating using discussions
 intro: Gather and discuss your project with community members and other maintainers.
 versions:
-  feature: discussions
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
 children:
   - /about-discussions
   - /participating-in-a-discussion
   - /collaborating-with-maintainers-using-discussions
 ---
-

content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md

@@ -3,7 +3,9 @@ title: Participating in a discussion
 intro: 'You can converse with the community and maintainers in a forum within the repository for a project on {% data variables.product.product_name %}.'
 permissions: 'People with read access to a repository can participate in discussions and polls in the repository. People with read access to the source repository for organization discussions can participate in discussions and polls in that organization. {% data reusables.enterprise-accounts.emu-permission-interact %}'
 versions:
-  feature: discussions
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
 shortTitle: Participate in discussion
 ---
 

content/discussions/guides/best-practices-for-community-conversations-on-github.md

@@ -3,7 +3,9 @@ title: Best practices for community conversations on GitHub
 shortTitle: Best practices for community conversations
 intro: 'You can use discussions to brainstorm with your team, and eventually move the conversation to an issue when you are ready to scope out the work.'
 versions:
-  feature: discussions
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
 ---
 
 

content/discussions/guides/finding-your-discussions.md

@@ -2,7 +2,9 @@
 title: Finding your discussions
 intro: You can easily access every discussion you've created or participated in.
 versions:
-  feature: discussions
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
 shortTitle: Find discussions
 redirect_from:
   - /discussions/guides/finding-discussions-across-multiple-repositories

content/discussions/guides/granting-higher-permissions-to-top-contributors.md

@@ -2,7 +2,9 @@
 title: Granting higher permissions to top contributors
 intro: Repository administrators can promote any community member to a moderator and maintainer.
 versions:
-  feature: discussions
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
 shortTitle: Grant higher permissions
 ---
 

content/discussions/guides/index.md

@@ -3,10 +3,11 @@ title: Discussions guides
 shortTitle: Guides
 intro: Discover pathways to get started or learn best practices for participating or monitoring your community's discussions.
 versions:
-  feature: discussions
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
 children:
   - /best-practices-for-community-conversations-on-github
   - /finding-your-discussions
   - /granting-higher-permissions-to-top-contributors
 ---
-

content/discussions/index.md

@@ -32,7 +32,9 @@ changelog:
 examples_source: data/product-examples/discussions/community-examples.yml
 layout: product-landing
 versions:
-  feature: discussions
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
 communityRedirect:
   name: Provide GitHub Feedback
   href: 'https://github.com/orgs/community/discussions/categories/discussions'

content/discussions/managing-discussions-for-your-community/creating-discussion-category-forms.md

@@ -3,7 +3,9 @@ title: Creating discussion category forms
 shortTitle: Create discussion category forms
 intro: You can customize the templates that are available for community members to use when they open new discussions in your repository.
 versions:
-  feature: discussion-category-forms
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
 ---
 
 ## About discussion category forms

content/discussions/managing-discussions-for-your-community/index.md

@@ -3,7 +3,9 @@ title: Managing discussions for your community
 shortTitle: Managing discussions
 intro: 'You can enable and configure {% data variables.product.prodname_discussions %} for your repository, and you can use tools on {% data variables.product.product_name %} to moderate conversations among community members.'
 versions:
-  feature: discussions
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
 children:
   - /managing-discussions
   - /managing-categories-for-discussions
@@ -12,4 +14,3 @@ children:
   - /creating-discussion-category-forms
   - /syntax-for-discussion-category-forms
 ---
-

content/discussions/managing-discussions-for-your-community/managing-categories-for-discussions.md

@@ -3,7 +3,9 @@ title: Managing categories for discussions
 intro: 'You can categorize discussions to organize conversations for your community members, and you can choose a format for each category.'
 permissions: Repository administrators and people with write or greater access to a repository can manage categories for discussions in the repository. Repository administrators and people with write or greater access to the source repository for organization discussions can manage categories for discussions in the organization.
 versions:
-  feature: discussions
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
 shortTitle: Manage categories
 redirect_from:
   - /discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository
@@ -18,8 +20,7 @@ redirect_from:
 
 Each category must have a unique name and emoji pairing, and can be accompanied by a detailed description stating its purpose. Categories help maintainers organize how conversations are filed and are customizable to help distinguish categories that are Q&A or more open-ended conversations. {% data reusables.discussions.repository-category-limit %} For more information, see [AUTOTITLE](/discussions/collaborating-with-your-community-using-discussions/about-discussions#about-categories-and-formats-for-discussions).
 
-{% ifversion discussions-category-section %}
+{% data reusables.discussions.category-sections %}
-{% data reusables.discussions.category-sections %}{% endif %}
 
 ## Default categories
 
@@ -42,12 +43,9 @@ Each category must have a unique name and emoji pairing, and can be accompanied
    ![Screenshot of the "Manage discussion categories" page. A button, labeled "New category", is highlighted with an orange outline.](/assets/images/help/discussions/click-new-category-button.png)
 
 1. {% data reusables.discussions.edit-category-details %}
-{% ifversion discussions-category-section %}
+{% data reusables.discussions.add-category-to-section %}
-{% data reusables.discussions.add-category-to-section %}{% endif %}
 1. Click **Create**.
 
-{% ifversion discussions-category-section %}
-
 ## Creating a section
 
 1. Navigate to the main page of the repository or organization where you want to create a category.
@@ -58,7 +56,6 @@ Each category must have a unique name and emoji pairing, and can be accompanied
 1. Edit the emoji and title of the section.
 1. Select the categories that you want to add to the section. A category can only belong to one section at a time.
 1. Click **Create**.
-{% endif %}
 
 ## Editing a category
 
@@ -69,12 +66,9 @@ You can edit a category to change the category's emoji, title, description, and
 {% data reusables.discussions.edit-categories %}
 1. To the right of a category in the list, click {% octicon "pencil" aria-label="The pencil icon" %}.
 1. {% data reusables.discussions.edit-category-details %}
-{% ifversion discussions-category-section %}
+{% data reusables.discussions.add-category-to-section %}
-{% data reusables.discussions.add-category-to-section %}{% endif %}
 1. Click **Save changes**.
 
-{% ifversion discussions-category-section %}
-
 ## Editing a section
 
 You can edit a section to change the section's emoji and title, and to add and remove categories from the section.
@@ -85,13 +79,12 @@ You can edit a section to change the section's emoji and title, and to add and r
 1. To the right of a section in the list, click {% octicon "pencil" aria-label="The pencil icon" %}.
 1. Edit the section's emoji and title, and select or deselect the categories that you want to add or remove from the section.
 1. Click **Update**.
-{% endif %}
 
 ## Deleting a category
 
 When you delete a category, {% data variables.product.product_name %} will move all discussions in the deleted category to an existing category that you choose.
 
-{% ifversion discussions-category-section %}When you delete a section, all categories within the section will no longer belong to a section.{% endif %}
+When you delete a section, all categories within the section will no longer belong to a section.
 
 1. Navigate to the main page of the repository or organization where you want to delete a category.
 {% data reusables.discussions.discussions-tab %}
@@ -99,8 +92,6 @@ When you delete a category, {% data variables.product.product_name %} will move
 1. Select the dropdown menu, and click a new category for any discussions in the category you're deleting.
 1. Click **Delete & Move**.
 
-{% ifversion discussions-category-section %}
-
 ## Deleting a section
 
 When you delete a section, all categories within the section will no longer belong to a section.
@@ -109,4 +100,3 @@ When you delete a section, all categories within the section will no longer belo
 {% data reusables.discussions.discussions-tab %}
 1. To the right of a section in the list, click {% octicon "trash" aria-label="The trash icon" %}.
 1. In the dialog box, review the information about deleting a section, then click **Delete**.
-{% endif %}

content/discussions/managing-discussions-for-your-community/managing-discussions.md

@@ -3,7 +3,9 @@ title: Managing discussions
 intro: 'You can categorize, spotlight, transfer, or delete the discussions.'
 permissions: Repository administrators and people with {% ifversion discussions-moderators-control-who-can-report %}triage{% else %}write{% endif %} or greater access to a repository can manage discussions in the repository. Repository administrators and people with {% ifversion discussions-moderators-control-who-can-report %}triage{% else %}write{% endif %} or greater access to the source repository for organization discussions can manage discussions in the organization.
 versions:
-  feature: discussions
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
 shortTitle: Manage discussions
 redirect_from:
   - /discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository
@@ -20,7 +22,7 @@ As a discussions maintainer, you can create community resources to encourage dis
 
 When a discussion yields an idea or bug that is ready to be worked on, you can create a new issue from a discussion. For more information, see [AUTOTITLE](/issues/tracking-your-work-with-issues/creating-an-issue#creating-an-issue-from-a-discussion).
 
-You can pin a discussion to the top of the list of discussions for the repository or organization. {% ifversion discussions-category-specific-pins %}You can also pin a discussion to a specific category.{% endif %} For more information, see [AUTOTITLE](/discussions/managing-discussions-for-your-community/managing-discussions#pinning-a-discussion).
+You can pin a discussion to the top of the list of discussions for the repository or organization. You can also pin a discussion to a specific category. For more information, see [AUTOTITLE](/discussions/managing-discussions-for-your-community/managing-discussions#pinning-a-discussion).
 
 For more information on facilitating a healthy discussion, see [AUTOTITLE](/communities/moderating-comments-and-conversations).
 
@@ -46,7 +48,6 @@ You can also move a discussion to a different category. It's not possible to mov
 
 ## Pinning a discussion
 
-{% ifversion discussions-category-specific-pins %}
 You can pin a discussion above the list of discussions for the repository or organization. You can also pin a discussion to a specific category. The globally pinned discussions will be shown in addition to the discussions pinned to a specific category.
 
 This is what it looks like when you have a globally pinned discussion and a discussion pinned to the Ideas category.
@@ -55,25 +56,18 @@ This is what it looks like when you have a globally pinned discussion and a disc
 
 ### Pinning a discussion globally
 
-{% endif %}
-
 You can pin up to four important discussions above the list of discussions for the repository or organization.
 
 {% data reusables.discussions.navigate-to-repo-or-org %}
 {% data reusables.discussions.discussions-tab %}
 {% data reusables.discussions.click-discussion-in-list %}
 1. In the right sidebar, click **{% octicon "pin" aria-hidden="true" %} Pin discussion**.
-{% ifversion discussions-category-specific-pins %}
 
-   ![Screenshot of the right sidebar of a discussion. The "Pin discussion" option is highlighted with an orange outline.](/assets/images/help/discussions/click-pin-discussion-with-category-pins.png){% else %}
+   ![Screenshot of the right sidebar of a discussion. The "Pin discussion" option is highlighted with an orange outline.](/assets/images/help/discussions/click-pin-discussion-with-category-pins.png)
-
-   ![Screenshot of the right sidebar of a discussion. The "Pin discussion" option is highlighted with an orange outline.](/assets/images/help/discussions/click-pin-discussion.png){% endif %}
 
 1. Optionally, customize the look of the pinned discussion.
 1. Click **Pin discussion**.
 
-{% ifversion discussions-category-specific-pins %}
-
 ### Pinning a discussion to a category
 
 You can pin up to four important discussions above the list of discussions in a specific category.
@@ -86,7 +80,6 @@ You can pin up to four important discussions above the list of discussions in a
    ![Screenshot of the right sidebar of a discussion. The "Pin discussion to Q&A" option is outlined in dark orange.](/assets/images/help/discussions/pin-discussion-to-category.png)
 
 1. To confirm, click **Pin to CATEGORY**.
-{% endif %}
 
 ## Editing a pinned discussion
 
@@ -95,22 +88,19 @@ Editing a pinned discussion will not change the discussion's category. For more
 {% data reusables.discussions.navigate-to-repo-or-org %}
 {% data reusables.discussions.discussions-tab %}
 {% data reusables.discussions.click-discussion-in-list %}
-1. In the right sidebar, click **{% octicon "pencil" aria-hidden="true" %} Edit pinned discussion**. {% ifversion discussions-category-specific-pins %}
+1. In the right sidebar, click **{% octicon "pencil" aria-hidden="true" %} Edit pinned discussion**.
 
-   ![Screenshot of the right sidebar of a discussion. The "Edit pinned discussion" option is outlined in dark orange.](/assets/images/help/discussions/edit-pinned-discussion-with-category-pins.png){% endif %}
+   ![Screenshot of the right sidebar of a discussion. The "Edit pinned discussion" option is outlined in dark orange.](/assets/images/help/discussions/edit-pinned-discussion-with-category-pins.png)
 1. Customize the look of the pinned discussion.
 1. Click **Pin discussion**.
 
 ## Unpinning a discussion
 
-{% ifversion discussions-category-specific-pins %}
-
 You can unpin a discussion from the list of discussions for the repository or organization, or from the list of discussions in a specific category.
 
 ### Unpinning a globally pinned discussion
 
 You can unpin a globally pinned discussion. This will not delete the discussion, but the discussion will no longer be displayed above the list of discussions.
-{% endif %}
 
 {% data reusables.discussions.navigate-to-repo-or-org %}
 {% data reusables.discussions.discussions-tab %}
@@ -121,8 +111,6 @@ You can unpin a globally pinned discussion. This will not delete the discussion,
 
 1. Read the warning, then click **Unpin discussion**.
 
-{% ifversion discussions-category-specific-pins %}
-
 ### Unpinning a discussion from a category
 
 You can unpin a discussion pinned to a specific category. This will not delete the discussion, but the discussion will no longer be displayed at the top of the category.
@@ -135,7 +123,6 @@ You can unpin a discussion pinned to a specific category. This will not delete t
    ![Screenshot of the right sidebar of a discussion. The "Unpin discussion from this category" option is outlined in dark orange.](/assets/images/help/discussions/unpin-discussion-from-category.png)
 
 1. Read the warning, then click **Unpin from this category**.
-{% endif %}
 
 ## Transferring a discussion
 
@@ -144,12 +131,9 @@ To transfer a discussion, you must have permissions to create discussions in the
 {% data reusables.discussions.navigate-to-repo-or-org %}
 {% data reusables.discussions.discussions-tab %}
 {% data reusables.discussions.click-discussion-in-list %}
-1. In the right sidebar, click {% octicon "arrow-right" aria-hidden="true" %} {% ifversion discussions-category-specific-pins %}**Transfer this discussion**{% else %}**Transfer discussion**{% endif %}.
+1. In the right sidebar, click {% octicon "arrow-right" aria-hidden="true" %}**Transfer this discussion**.
-{% ifversion discussions-category-specific-pins %}
 
-   ![Screenshot of the right sidebar of a discussion. The "Transfer this discussion" option is outlined in dark orange.](/assets/images/help/discussions/transfer-discussion-with-category-pin.png) {% else %}
+   ![Screenshot of the right sidebar of a discussion. The "Transfer this discussion" option is outlined in dark orange.](/assets/images/help/discussions/transfer-discussion-with-category-pin.png)
-
-   ![Screenshot of the right sidebar of a discussion. The "Transfer this discussion" option is outlined in dark orange.](/assets/images/help/discussions/click-transfer-discussion.png){% endif %}
 
 1. Select the repository you want to transfer the discussion to. You can also search for repositories. If you want to transfer a discussion to an organization, choose the source repository for the organization's discussions.
 1. Click **Transfer discussion**.
@@ -160,14 +144,11 @@ To transfer a discussion, you must have permissions to create discussions in the
 {% data reusables.discussions.discussions-tab %}
 {% data reusables.discussions.click-discussion-in-list %}
 1. In the right sidebar, click **{% octicon "trash" aria-hidden="true" %} Delete discussion**.
-{% ifversion discussions-category-specific-pins %}
 
-   ![Screenshot of the right sidebar of a discussion. The "Delete discussion" option is outlined in dark orange.](/assets/images/help/discussions/delete-discussion-with-category-pins.png){% endif %}
+   ![Screenshot of the right sidebar of a discussion. The "Delete discussion" option is outlined in dark orange.](/assets/images/help/discussions/delete-discussion-with-category-pins.png)
 
 1. Read the warning, then click **Delete this discussion**.
 
-{% ifversion discussions-closable %}
-
 ## Closing a discussion
 
 {% data reusables.discussions.closing-discussions %}
@@ -178,8 +159,6 @@ To transfer a discussion, you must have permissions to create discussions in the
 1. At the bottom of the discussion, below the comment box, click **Close discussion**.
 1. Optionally, to change the reason for closing the discussion, select the {% octicon "triangle-down" aria-label="The down triangle octicon" %} dropdown next to "Close discussion" and click a reason.
 
-{% endif %}
-
 ## Converting issues based on labels
 
 You can convert all issues with the same label to discussions in bulk. Future issues with this label will also automatically convert to the discussion and category you configure.

content/discussions/managing-discussions-for-your-community/moderating-discussions.md

@@ -3,7 +3,9 @@ title: Moderating discussions
 intro: 'You can promote healthy collaboration by marking comments as answers, locking or unlocking discussions, converting issues to discussions, and editing or deleting comments, discussions, and categories that don''t align with your{% ifversion fpt or ghec %} community''s code of conduct{% elsif ghes %} organization''s contribution guidelines{% endif %}.'
 permissions: People with triage access to a repository can moderate discussions in the repository. People with triage access to the source repository for organization discussions can moderate discussions in the organization.
 versions:
-  feature: discussions
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
 ---
 
 
@@ -17,15 +19,11 @@ versions:
 
 ## Locking discussions
 
-It's appropriate to lock a conversation when the entire conversation is not constructive or violates your community's code of conduct or {% data variables.product.prodname_dotcom %}'s [Community Guidelines](/free-pro-team@latest/site-policy/github-terms/github-community-guidelines). You can also lock a conversation to prevent comments on a discussion you want to use as an announcement to the community. When you lock a conversation, people with write access to the repository, or source repository for organization discussions, will still be able to comment on the discussion. {% ifversion discussions-lock-allow-reactions %}You can also allow emoji reactions to a locked discussion.{% endif %}
+It's appropriate to lock a conversation when the entire conversation is not constructive or violates your community's code of conduct or {% data variables.product.prodname_dotcom %}'s [Community Guidelines](/free-pro-team@latest/site-policy/github-terms/github-community-guidelines). You can also lock a conversation to prevent comments on a discussion you want to use as an announcement to the community. When you lock a conversation, people with write access to the repository, or source repository for organization discussions, will still be able to comment on the discussion. You can also allow emoji reactions to a locked discussion.
-
-{% ifversion discussions-closable %}
 
 > [!NOTE]
 > You can also close a discussion. For more information, see [Closing a discussion](/discussions/managing-discussions-for-your-community/managing-discussions#closing-a-discussion).
 
-{% endif %}
-
 {% data reusables.discussions.navigate-to-repo-or-org %}
 {% data reusables.discussions.discussions-tab %}
 1. In the list of discussions, click the discussion you want to lock.
@@ -33,8 +31,8 @@ It's appropriate to lock a conversation when the entire conversation is not cons
    ![Screenshot of the list of discussions with an unanswered discussion.](/assets/images/help/discussions/unanswered-discussion.png)
 
 1. In the right margin of a discussion, click **Lock conversation**.
-1. Read the information about locking conversations.{% ifversion discussions-lock-allow-reactions %}
+1. Read the information about locking conversations.
-1. Optionally, to allow emoji reactions while the discussion is locked, select **Allow reactions**.{% endif %}
+1. Optionally, to allow emoji reactions while the discussion is locked, select **Allow reactions**.
 1. To lock the conversation, click **Lock conversation**.
 1. When you're ready to unlock the conversation, click **Unlock conversation** in the right margin of a discussion, then click **Unlock conversation**.
 

content/discussions/managing-discussions-for-your-community/syntax-for-discussion-category-forms.md

@@ -3,7 +3,9 @@ title: Syntax for discussion category forms
 shortTitle: Syntax for discussion category forms
 intro: You can use YAML syntax to define the fields in your discussion category forms.
 versions:
-  feature: discussion-category-forms
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
 ---
 
 ## About YAML syntax for discussion category forms

content/discussions/managing-discussions-for-your-community/viewing-insights-for-your-discussions.md

@@ -3,7 +3,9 @@ title: Viewing insights for your discussions
 intro: 'Discussions insights provide data about your discussions'' activity, views, and contributors.'
 permissions: Repository administrators and people with maintain access to a repository can view the insights dashboard for discussions in that repository. Repository administrators and people with maintain access to the source repository for organization discussions can view the insights dashboard for discussions in that organization.
 versions:
-  feature: discussions
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
 topics:
   - Discussions
 shortTitle: View discussions insights

content/discussions/quickstart.md

@@ -3,7 +3,9 @@ title: Quickstart for GitHub Discussions
 intro: 'Enable {% data variables.product.prodname_discussions %} on an existing repository or organization and start conversations with your community.'
 allowTitleToDifferFromFilename: true
 versions:
-  feature: discussions
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
 shortTitle: Quickstart
 ---
 

content/get-started/accessibility/github-command-palette.md

@@ -41,8 +41,8 @@ When you open the command palette, it shows your location at the top left and us
 ![Screenshot of the command palette. "octo-org" is highlighted with an orange outline.](/assets/images/help/command-palette/command-palette-launch.png)
 
 > [!NOTE]
-> * If you are editing Markdown text, open the command palette with <kbd>Ctrl</kbd>+<kbd>Alt</kbd>+<kbd>K</kbd> (Windows and Linux) or <kbd>Command</kbd>+<kbd>Option</kbd>+<kbd>K</kbd> (Mac).{% ifversion projects-v2 %}
+> * If you are editing Markdown text, open the command palette with <kbd>Ctrl</kbd>+<kbd>Alt</kbd>+<kbd>K</kbd> (Windows and Linux) or <kbd>Command</kbd>+<kbd>Option</kbd>+<kbd>K</kbd> (Mac).
-> * If you are working on a {% data variables.projects.project_v2 %}, a project-specific command palette is displayed instead. For more information, see [AUTOTITLE](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/changing-the-layout-of-a-view).{% endif %}
+> * If you are working on a {% data variables.projects.project_v2 %}, a project-specific command palette is displayed instead. For more information, see [AUTOTITLE](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/changing-the-layout-of-a-view).
 
 ### Customizing your {% data variables.product.prodname_command_palette %} keyboard shortcuts
 

content/get-started/accessibility/keyboard-shortcuts.md

@@ -18,8 +18,7 @@ versions:
 
 Typing <kbd>?</kbd> on {% data variables.product.prodname_dotcom %} brings up a dialog box that lists the keyboard shortcuts available for that page. You can use these keyboard shortcuts to perform actions across the site without using your mouse to navigate.
 
-{% ifversion keyboard-shortcut-accessibility-setting %}
+You can disable character key shortcuts, while still allowing shortcuts that use modifier keys, in your accessibility settings. For more information, see [AUTOTITLE](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-user-account-settings/managing-accessibility-settings).
-You can disable character key shortcuts, while still allowing shortcuts that use modifier keys, in your accessibility settings. For more information, see [AUTOTITLE](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-user-account-settings/managing-accessibility-settings).{% endif %}
 
 {% ifversion command-palette %}
 The {% data variables.product.prodname_command_palette %} also gives you quick access to a wide range of actions, without the need to remember keyboard shortcuts. For more information, see [AUTOTITLE](/get-started/accessibility/github-command-palette).
@@ -49,9 +48,7 @@ The following sections list some of the available keyboard shortcuts, organized
 |<kbd>G</kbd> <kbd>B</kbd> | Go to the **Projects** tab. For more information, see [AUTOTITLE](/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards).
 | {% endif %} |
 |<kbd>G</kbd> <kbd>W</kbd> | Go to the **Wiki** tab. For more information, see [AUTOTITLE](/communities/documenting-your-project-with-wikis/about-wikis). |
-|  {% ifversion discussions %} |
 |<kbd>G</kbd> <kbd>G</kbd> | Go to the **Discussions** tab. For more information, see [AUTOTITLE](/discussions/collaborating-with-your-community-using-discussions/about-discussions).
-| {% endif %} |
 
 ## Source code editing
 
@@ -175,8 +172,6 @@ If you view a code file in a repository using the **Code** view and click on any
 |<kbd>Option</kbd> and click (Mac) or <kbd>Alt</kbd> and click (Windows/Linux) | Toggle between collapsing and expanding all outdated or resolved review comments in a pull request (for example, by holding down <kbd>Alt</kbd> and clicking **Show outdated** or **Hide outdated**) |
 |Click, then <kbd>Shift</kbd> and click | Comment on multiple lines of a pull request by clicking a line number, holding <kbd>Shift</kbd>, then clicking another line number. For more information, see [AUTOTITLE](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request).|
 
-{% ifversion projects-v2 %}
-
 ## {% data variables.projects.projects_v2_caps %}
 
 ### Navigating a project
@@ -197,13 +192,11 @@ If you view a code file in a repository using the **Code** view and click on any
 |<kbd>Escape</kbd> | Cancel editing for the focused cell |
 |<kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>\ </kbd>(Mac) or <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>\ </kbd>(Windows/Linux) | Open row actions menu |
 |<kbd>Shift</kbd>+<kbd>Space</kbd> | Select item |
-|<kbd>Shift</kbd>+<kbd>↓</kbd> | Add cell {% ifversion projects-v2-board-keyboard-shorts %} or card{% endif %} below to selection |
+|<kbd>Shift</kbd>+<kbd>↓</kbd> | Add cell or card below to selection |
-|<kbd>Shift</kbd>+<kbd>↑</kbd> | Add cell {% ifversion projects-v2-board-keyboard-shorts %}or card{% endif %} above to selection |
+|<kbd>Shift</kbd>+<kbd>↑</kbd> | Add cell or card above to selection |
 |<kbd>Space</kbd> | Open selected item |
 |<kbd>e</kbd> | Archive selected items |
 
-{% ifversion projects-v2-board-keyboard-shorts %}
-
 ### Moving cards on the board layout
 
 | Keyboard shortcut | Description |
@@ -220,10 +213,6 @@ If you view a code file in a repository using the **Code** view and click on any
 |<kbd>→</kbd> | Move card(s) right |
 |<kbd>Command</kbd>+<kbd>→</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>→</kbd> (Windows/Linux) | Move card(s) to the rightmost column |
 
-{% endif %}
-
-{% endif %}
-
 {% ifversion projects-v1 %}
 
 ## {% data variables.product.prodname_projects_v1_caps %}

content/get-started/exploring-integrations/featured-github-integrations.md

@@ -46,8 +46,6 @@ You can integrate Jira Cloud with your personal or organization account to scan
 
 {% endif %}
 
-{% ifversion slack-and-team-integrations %}
-
 ## Team communication tools
 
 You can integrate your {% ifversion fpt or ghec %}personal{% elsif ghes %}user{% endif %} or organization account on {% data variables.location.product_location %} with third-party team communication tools, such as Slack or Microsoft Teams.
@@ -83,5 +81,3 @@ The {% data variables.product.prodname_dotcom %} for Teams app lets you subscrib
 You can also open and close issues, comment on your issues and pull requests, approve deployments, and see detailed references to issues and pull requests without leaving Microsoft Teams. The app will also ping you personally on Teams if you are mentioned as part of any {% data variables.product.prodname_dotcom %} notifications that you receive in your channels or personal chats.
 
 For more information, see the integration's [README](https://github.com/integrations/microsoft-teams/blob/master/Readme.md) in the `integrations/microsoft-teams` repository.
-
-{% endif %}

content/get-started/onboarding/getting-started-with-your-github-account.md

@@ -153,12 +153,9 @@ Notifications provide updates about the activity on {% data variables.product.pr
 
 You can use {% data variables.product.prodname_pages %} to create and host a website directly from a repository on {% data variables.location.product_location %}. For more information, see [AUTOTITLE](/pages/getting-started-with-github-pages/about-github-pages).
 
-{% ifversion discussions %}
-
 ### 9. Using {% data variables.product.prodname_discussions %}
 
 You can enable {% data variables.product.prodname_discussions %} for your repository to help build a community around your project. Maintainers, contributors and visitors can use discussions to share announcements, ask and answer questions, and participate in conversations around goals. For more information, see [AUTOTITLE](/discussions/collaborating-with-your-community-using-discussions/about-discussions).
-{% endif %}
 
 ## Part 4: Customizing and automating your work on {% data variables.product.product_name %}
 

content/get-started/using-github/communicating-on-github.md

@@ -22,14 +22,10 @@ topics:
 
 {% data variables.product.product_name %} provides built-in collaborative communication tools allowing you to interact closely with your community. This quickstart guide will show you how to pick the right tool for your needs.
 
-{% ifversion discussions %}
+{% ifversion team-discussions %}
-  {% ifversion team-discussions %}
+You can create and participate in issues, pull requests, {% data variables.product.prodname_discussions %}, and team discussions, depending on the type of conversation you'd like to have.
-  You can create and participate in issues, pull requests, {% data variables.product.prodname_discussions %}, and team discussions, depending on the type of conversation you'd like to have.
-  {% else %}
-  You can create and participate in issues, pull requests, and {% data variables.product.prodname_discussions %}, depending on the type of conversation you'd like to have.
-  {% endif %}
 {% else %}
-You can create and participate in issues, pull requests and team discussions, depending on the type of conversation you'd like to have.
+You can create and participate in issues, pull requests, and team discussions, depending on the type of conversation you'd like to have.
 {% endif %}
 
 ### {% data variables.product.prodname_github_issues %}
@@ -109,8 +105,6 @@ The **Files changed** tab of the pull request shows the implemented fix.
 * The user creates a pull request with the fix.
 * A repository maintainer reviews the pull request, comments on it, and merges it.
 
-{% ifversion discussions %}
-
 ### Scenarios for {% data variables.product.prodname_discussions %}
 
 * I have a question that's not necessarily related to specific files in the repository.
@@ -126,7 +120,6 @@ This example shows the {% data variables.product.prodname_discussions %} welcome
 
 This community maintainer started a discussion to welcome the community, and to ask members to introduce themselves. This post fosters an inviting atmosphere for visitors and contributors. The post also clarifies that the team's happy to help with contributions to the repository.
 
-{% endif %}
 {% ifversion team-discussions %}
 
 ### Scenarios for team discussions
@@ -184,9 +177,7 @@ For issues, for example, you can tag issues with labels for quicker searching an
 
 For pull requests, you can create draft pull requests if your proposed changes are still a work in progress. Draft pull requests cannot be merged until they're marked as ready for review. For more information, see [AUTOTITLE](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests#draft-pull-requests).
 
-{% ifversion discussions %}
 For {% data variables.product.prodname_discussions %}, you can{% ifversion fpt or ghec %} set up a code of conduct and{% endif %} pin discussions that contain important information for your community. For more information, see [AUTOTITLE](/discussions/collaborating-with-your-community-using-discussions/about-discussions).
-{% endif %}
 
 {% ifversion team-discussions %}For team discussions, you can edit or delete discussions on a team's page, and you can configure notifications for team discussions. For more information, see [AUTOTITLE](/organizations/collaborating-with-your-team/about-team-discussions).{% endif %}
 

content/get-started/using-github/github-flow.md

@@ -67,7 +67,7 @@ If your repository has checks configured to run on pull requests, you will see a
 
 ### Address review comments
 
-Reviewers should leave questions, comments, and suggestions. Reviewers can comment on the whole pull request or add comments to specific lines{% ifversion pull-request-comment-on-file %} or files{% endif %}. You and reviewers can insert images or code suggestions to clarify comments. For more information, see [AUTOTITLE](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests).
+Reviewers should leave questions, comments, and suggestions. Reviewers can comment on the whole pull request or add comments to specific lines or files. You and reviewers can insert images or code suggestions to clarify comments. For more information, see [AUTOTITLE](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests).
 
 You can continue to commit and push changes in response to the reviews. Your pull request will update automatically.
 

content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/about-writing-and-formatting-on-github.md

@@ -22,8 +22,6 @@ You can also interact with other users in pull requests and issues using feature
 
 Every comment field on {% data variables.product.product_name %} contains a text formatting toolbar, which allows you to format your text without learning Markdown syntax. In addition to Markdown formatting like bold and italic styles and creating headers, links, and lists, the toolbar includes {% data variables.product.product_name %}-specific features such as @-mentions, task lists, and links to issues and pull requests.
 
-{% ifversion fixed-width-font-gfm-fields %}
-
 ## Enabling fixed-width fonts in the editor
 
 You can enable a fixed-width font in every comment field on {% data variables.product.product_name %}. Each character in a fixed-width, or monospace, font occupies the same horizontal space. This can make it easier to edit advanced Markdown structures such as tables and code snippets.
@@ -35,8 +33,6 @@ You can enable a fixed-width font in every comment field on {% data variables.pr
 1. Under "Markdown editor font preference", select **Use a fixed-width (monospace) font when editing Markdown**.
    ![Screenshot of {% data variables.product.prodname_dotcom %} user settings for Markdown preference. The checkbox to use a fix-width font in Markdown is checked and outlined in dark orange.](/assets/images/help/writing/enable-fixed-width.png)
 
-{% endif %}
-
 ## Further reading
 
 * [{% data variables.product.prodname_dotcom %} Flavored Markdown Spec](https://github.github.com/gfm/)

content/get-started/writing-on-github/working-with-advanced-formatting/writing-mathematical-expressions.md

@@ -17,11 +17,7 @@ Mathematical expressions rendering is available in {% data variables.product.pro
 
 ## Writing inline expressions
 
-{% ifversion math-backtick-syntax %}
 There are two options for delimiting a math expression inline with your text. You can either surround the expression with dollar symbols (`$`), or start the expression with <code>$\`</code> and end it with <code>\`$</code>. The latter syntax is useful when the expression you are writing contains characters that overlap with markdown syntax. For more information, see [AUTOTITLE](/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax).
-{% else %}
-To include a math expression inline within your text, delimit the expression with dollar symbols `$`.
-{% endif %}
 
 ```text
 This sentence uses `$` delimiters to show math inline: $\sqrt{3x-1}+(1+x)^2$
@@ -29,14 +25,11 @@ This sentence uses `$` delimiters to show math inline: $\sqrt{3x-1}+(1+x)^2$
 
 ![Screenshot of rendered Markdown showing an inline mathematical expression: the square root of 3x minus 1 plus (1 plus x) squared.](/assets/images/help/writing/inline-math-markdown-rendering.png)
 
-{% ifversion math-backtick-syntax %}
-
 ```text
 This sentence uses $\` and \`$ delimiters to show math inline: $`\sqrt{3x-1}+(1+x)^2`$
 ```
 
 ![Screenshot of rendered Markdown showing an inline mathematical expression with backtick syntax: the square root of 3x minus 1 plus (1 plus x) squared.](/assets/images/help/writing/inline-backtick-math-markdown-rendering.png)
-{% endif %}
 
 ## Writing expressions as blocks
 
@@ -51,8 +44,6 @@ $$\left( \sum_{k=1}^n a_k b_k \right)^2 \leq \left( \sum_{k=1}^n a_k^2 \right) \
 
 ![Screenshot of rendered Markdown showing a complex equation. Bold text reads "The Cauchy-Schwarz Inequality" above the formula for the inequality.](/assets/images/help/writing/math-expression-as-a-block-rendering.png)
 
-{% ifversion math-fenced-blocks %}
-
 Alternatively, you can use the <code>\`\`\`math</code> code block syntax to display a math expression as a block. With this syntax, you don't need to use `$$` delimiters. The following will render the same as above:
 
 ````text
@@ -63,8 +54,6 @@ Alternatively, you can use the <code>\`\`\`math</code> code block syntax to disp
 ```
 ````
 
-{% endif %}
-
 ## Writing dollar signs in line with and within mathematical expressions
 
 To display a dollar sign as a character in the same line as a mathematical expression, you need to escape the non-delimiter `$` to ensure the line renders correctly.

content/graphql/guides/using-the-graphql-api-for-discussions.md

@@ -2,7 +2,9 @@
 title: Using the GraphQL API for Discussions
 intro: 'Learn how to use the {% data variables.product.prodname_discussions %} GraphQL API.'
 versions:
-  feature: discussions
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
 shortTitle: Use GraphQL for Discussions
 ---
 

content/issues/tracking-your-work-with-issues/about-issues.md

@@ -54,12 +54,9 @@ To help contributors open meaningful issues that provide the information that yo
 You can @mention collaborators who have access to your repository in an issue to draw their attention to a comment. To link related issues in the same repository, you can type `#` followed by part of the issue title and then clicking the issue that you want to link. To communicate responsibility, you can assign issues. If you find yourself frequently typing the same comment, you can use saved replies.
 {% ifversion fpt or ghec %} See [AUTOTITLE](/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax) and [AUTOTITLE](/issues/tracking-your-work-with-issues/assigning-issues-and-pull-requests-to-other-github-users).
 {% endif %}
-{% ifversion discussions %}
 
 ## Comparing issues and discussions
 
 Some conversations are more suitable for {% data variables.product.prodname_discussions %}. {% data reusables.discussions.you-can-use-discussions %} For guidance on when to use an issue or a discussion, see [AUTOTITLE](/get-started/using-github/communicating-on-github).
 
 When a conversation in an issue is better suited for a discussion, you can convert the issue to a discussion.
-
-{% endif %}

content/issues/tracking-your-work-with-issues/using-issues/creating-an-issue.md

@@ -97,8 +97,6 @@ You can open a new issue from a specific line or lines of code in a file or pull
 {% data reusables.repositories.assign-an-issue-as-project-maintainer %}
 {% data reusables.repositories.submit-new-issue %}
 
-{% ifversion discussions %}
-
 ## Creating an issue from discussion
 
 People with triage permission to a repository can create an issue from a discussion.
@@ -115,8 +113,6 @@ When you create an issue from a discussion, the contents of the discussion post
 {% data reusables.repositories.assign-an-issue-as-project-maintainer %}
 {% data reusables.repositories.submit-new-issue %}
 
-{% endif %}
-
 {% ifversion projects-v2-create-issue-modal %}
 
 ## Creating an issue from a project

content/organizations/managing-organization-settings/enabling-or-disabling-github-discussions-for-an-organization.md

@@ -3,7 +3,9 @@ title: Enabling or disabling GitHub Discussions for an organization
 intro: 'You can use {% data variables.product.prodname_discussions %} in an organization as a place for your organization to have conversations that aren''t specific to a single repository within your organization.'
 permissions: 'Organization owners can enable {% data variables.product.prodname_discussions %} for their organization.'
 versions:
-  feature: discussions
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
 topics:
   - Organizations
 shortTitle: Organization discussions

content/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization.md

@@ -5,7 +5,9 @@ redirect_from:
   - /github/setting-up-and-managing-organizations-and-teams/managing-discussion-creation-for-repositories-in-your-organization
 permissions: Organization owners can manage discussion creation for repositories owned by the organization.
 versions:
-  feature: discussions
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
 topics:
   - Organizations
   - Teams

content/packages/index.md

@@ -12,11 +12,11 @@ featuredLinks:
     - /packages/learn-github-packages/installing-a-package
   popular:
     - /packages/working-with-a-github-packages-registry/working-with-the-npm-registry
-    - '{% ifversion docker-ghcr-enterprise-migration %}/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry{% endif %}'
+    - '{% ifversion ghes %}/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry{% endif %}'
     - /packages/learn-github-packages
     - /packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry
   guideCards:
-    - '{% ifversion docker-ghcr-enterprise-migration %}/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry{% endif %}'
+    - '{% ifversion ghes %}/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry{% endif %}'
     - /packages/working-with-a-github-packages-registry/working-with-the-container-registry
     - '{% ifversion packages-npm-v2 %}/packages/working-with-a-github-packages-registry/working-with-the-npm-registry{% endif %}'
     - /packages/working-with-a-github-packages-registry/working-with-the-rubygems-registry

content/packages/learn-github-packages/about-permissions-for-github-packages.md

@@ -19,7 +19,7 @@ The following {% data variables.product.prodname_registry %} registries support
 
 * {% data variables.product.prodname_container_registry %}
 {%- ifversion packages-npm-v2 %}
-* npm registry
+* npm registry <!-- markdownlint-disable-line GHD034 -->
 {%- endif %}
 {%- ifversion packages-nuget-v2 %}
 * NuGet registry
@@ -38,7 +38,7 @@ The following {% data variables.product.prodname_registry %} registries **only**
 * Docker registry (`docker.pkg.github.com`)
 {%- endif %}
 {%- ifversion packages-npm-v2 %}{% else %}
-* npm registry
+* npm registry <!-- markdownlint-disable-line GHD034 -->
 {%- endif %}
 * Apache Maven registry
 * Gradle registry
@@ -49,7 +49,7 @@ The following {% data variables.product.prodname_registry %} registries **only**
 * RubyGems registry
 {%- endif %}
 
-For {% ifversion ghes %}the {% data variables.product.prodname_container_registry %}{% else %}other registries{% endif %}, you can choose to allow packages to be scoped to a user or an organization, or linked to a repository. {% ifversion docker-ghcr-enterprise-migration %}For information about migration to the {% data variables.product.prodname_container_registry %}, see [AUTOTITLE](/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry).{% endif %}
+For {% ifversion ghes %}the {% data variables.product.prodname_container_registry %}{% else %}other registries{% endif %}, you can choose to allow packages to be scoped to a user or an organization, or linked to a repository. {% ifversion ghes %}For information about migration to the {% data variables.product.prodname_container_registry %}, see [AUTOTITLE](/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry).{% endif %}
 
 ## Visibility and access permissions for packages
 

content/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry.md

@@ -1,6 +1,6 @@
 ---
 title: Migrating to the Container registry from the Docker registry
-intro: '{% ifversion docker-ghcr-enterprise-migration %}An enterprise owner can{% else %}{% data variables.product.company_short %} will{% endif %} migrate Docker images previously stored in the Docker registry on {% data variables.product.github %} to the {% data variables.product.prodname_container_registry %}.'
+intro: '{% ifversion ghes %}An enterprise owner can{% else %}{% data variables.product.company_short %} will{% endif %} migrate Docker images previously stored in the Docker registry on {% data variables.product.github %} to the {% data variables.product.prodname_container_registry %}.'
 product: '{% data reusables.gated-features.packages %}'
 redirect_from:
   - /packages/getting-started-with-github-container-registry/migrating-to-github-container-registry-for-docker-images
@@ -9,7 +9,7 @@ redirect_from:
 versions:
   fpt: '*'
   ghec: '*'
-  feature: docker-ghcr-enterprise-migration
+  ghes: '*'
 shortTitle: Migration to Container registry
 topics:
   - Containers
@@ -25,9 +25,9 @@ topics:
 
 ## About migration from the Docker registry
 
-{% data reusables.package_registry.container-registry-replaces-docker-registry %} If you've stored Docker images in the Docker registry, {% ifversion docker-ghcr-enterprise-migration %}an enterprise owner{% else %}{% data variables.product.company_short %}{% endif %} will gradually migrate the images to the {% data variables.product.prodname_container_registry %}. No action is required on your part.
+{% data reusables.package_registry.container-registry-replaces-docker-registry %} If you've stored Docker images in the Docker registry, {% ifversion ghes %}an enterprise owner{% else %}{% data variables.product.company_short %}{% endif %} will gradually migrate the images to the {% data variables.product.prodname_container_registry %}. No action is required on your part.
 
-{% ifversion docker-ghcr-enterprise-migration %}
+{% ifversion ghes %}
 
 > [!NOTE]
 > {% data reusables.package_registry.container-registry-ghes-migration-availability %} For more information about finding the version of {% data variables.product.product_name %} that you use, see [AUTOTITLE](/get-started/learning-about-github/about-versions-of-github-docs#github-enterprise-server).
@@ -53,9 +53,7 @@ After migration, you'll no longer be able to use the GraphQL API to query for pa
 
 For more information about billing for the {% data variables.product.prodname_container_registry %}, see [AUTOTITLE](/billing/managing-billing-for-github-packages/about-billing-for-github-packages).
 
-{% endif %}
+{% else %}
-
-{% ifversion docker-ghcr-enterprise-migration %}
 
 ## Further reading
 

content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches.md

@@ -55,7 +55,7 @@ Now when you merge the `feature2` pull request, it'll be merged into the `main`
 
 ## Working with protected branches
 
-Repository administrators {% ifversion edit-repository-rules %}or custom roles with the "edit repository rules" permission {% endif %}can enable protections on a branch. If you're working on a branch that's protected, you won't be able to delete or force push to the branch. Repository administrators can additionally enable several other protected branch settings to enforce various workflows before a branch can be merged.
+Repository administrators or custom roles with the "edit repository rules" permission can enable protections on a branch. If you're working on a branch that's protected, you won't be able to delete or force push to the branch. Repository administrators can additionally enable several other protected branch settings to enforce various workflows before a branch can be merged.
 
 > [!NOTE]
 > If you're a repository administrator, you can merge pull requests on branches with branch protections enabled even if the pull request does not meet the requirements, unless branch protections have been set to "Include administrators."

content/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/managing-a-branch-protection-rule.md

@@ -23,7 +23,7 @@ versions:
   fpt: '*'
   ghes: '*'
   ghec: '*'
-permissions: 'People with admin permissions {% ifversion edit-repository-rules %}or a custom role with the "edit repository rules" permission{% endif %} to a repository can manage branch protection rules.'
+permissions: 'People with admin permissions or a custom role with the "edit repository rules" permission to a repository can manage branch protection rules.'
 topics:
   - Repositories
 shortTitle: Branch protection rule

content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/enabling-or-disabling-github-discussions-for-a-repository.md

@@ -3,7 +3,9 @@ title: Enabling or disabling GitHub Discussions for a repository
 intro: 'You can use {% data variables.product.prodname_discussions %} in a repository as a place for your community to have conversations, ask questions, and post answers without scoping work in an issue.'
 permissions: 'People with admin permissions to a repository can enable {% data variables.product.prodname_discussions %} for the repository.'
 versions:
-  feature: discussions
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
 topics:
   - Repositories
 redirect_from:

content/rest/enterprise-admin/manage-ghes.md

@@ -32,8 +32,6 @@ To authenticate requests to endpoints for the Manage {% data variables.product.p
 curl -L -u "api_key:ROOT-SITE-ADMINISTRATOR-PASSWORD" 'http(s)://HOSTNAME:ADMINISTRATION-PORT/manage'
 ```
 
-{% ifversion enterprise-management-console-multi-user-auth %}
-
 ### Authentication as a {% data variables.enterprise.management_console %} user
 
 {% data variables.enterprise.management_console %} user accounts can also authenticate to access these endpoints. For more information, see [AUTOTITLE](/admin/configuration/administering-your-instance-from-the-management-console/managing-access-to-the-management-console#management-console-user).
@@ -44,8 +42,6 @@ To authenticate with the password for a {% data variables.enterprise.management_
 curl -L -u "YOUR_USER_NAME:YOUR_PASSWORD" 'http(s)://HOSTNAME:ADMINISTRATION-PORT/manage'
 ```
 
-{% endif %}
-
 ### Query parameters
 
 By default, the response includes information from about all configured nodes for the instance. On an instance with multiple nodes, the details originate from `/data/user/common/cluster.conf`. You can use the following query parameters to filter the response for information about specific nodes.

content/rest/enterprise-admin/management-console.md

@@ -44,9 +44,9 @@ If you cannot provide a port number, you'll need to configure your tool to autom
 
 You may also need to add the [`-k` flag](http://curl.haxx.se/docs/manpage.html#-k) when using `curl`, since {% data variables.product.product_name %} uses a self-signed certificate before you [add your own TLS certificate](/admin/configuration/configuring-network-settings/configuring-tls).
 
-### Authentication {% ifversion enterprise-management-console-multi-user-auth %}as the root site administrator{% endif %}
+### Authentication as the root site administrator
 
-You need to pass your [{% ifversion enterprise-management-console-multi-user-auth %}root site administrator{% else %}{% data variables.enterprise.management_console %}{% endif %} password](/admin/configuration/administering-your-instance-from-the-management-console/managing-access-to-the-management-console) as an authentication token to every endpoint in this category except [Create a {% data variables.product.github %} license](#create-a-github-license).
+You need to pass your [root site administrator password](/admin/configuration/administering-your-instance-from-the-management-console/managing-access-to-the-management-console) as an authentication token to every endpoint in this category except [Create a {% data variables.product.github %} license](#create-a-github-license).
 
 Use the `api_key` parameter to send this token with each request. For example:
 
@@ -60,8 +60,6 @@ You can also use standard HTTP authentication to send this token. For example:
 curl -L -u "api_key:YOUR_PASSWORD" 'https://HOSTNAME:ADMIN-PORT/setup/api'
 ```
 
-{% ifversion enterprise-management-console-multi-user-auth %}
-
 ### Authentication as a {% data variables.enterprise.management_console %} user
 
 [Management Console user accounts](/admin/configuration/administering-your-instance-from-the-management-console/managing-access-to-the-management-console#management-console-user) can also authenticate to access this endpoint.
@@ -72,6 +70,4 @@ To authenticate with the password for a {% data variables.enterprise.management_
 curl -L -u "YOUR_USER_NAME:YOUR_PASSWORD" 'https://HOSTNAME:ADMIN-PORT/setup/api'
 ```
 
-{% endif %}
-
 <!-- Content after this section is automatically generated -->

content/search-github/searching-on-github/searching-discussions.md

@@ -2,7 +2,9 @@
 title: Searching discussions
 intro: 'You can search for discussions on {% data variables.product.product_name %} and narrow the results using search qualifiers.'
 versions:
-  feature: discussions
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
 topics:
   - GitHub search
 redirect_from:

content/webhooks/using-webhooks/delivering-webhooks-to-private-systems.md

@@ -14,11 +14,11 @@ You may want to deliver {% data variables.product.company_short %} webhooks to p
 
 A reverse proxy is a web server that sits between a client and an application. The reverse proxy receives requests from the client and forwards them to the application. This ensures no direct communication occurs between clients on the internet and the underlying application. A variety of systems can serve a reverse proxy, including:
 
-* web servers, like [nginx](https://docs.nginx.com/nginx/admin-guide/web-server/reverse-proxy/)
+* Web servers, like [nginx](https://docs.nginx.com/nginx/admin-guide/web-server/reverse-proxy/)
 * API gateways
-* free, open-source overlay networks, like [OpenZiti](https://openziti.io)
+* Free, open-source overlay networks, like [OpenZiti](https://openziti.io)
-* commercial ingress management tools, like [ngrok](https://ngrok.com/partners/github)
+* Commercial ingress management tools, like [ngrok](https://ngrok.com/partners/github)
-* free, open-source ingress management tools, like [zrok](https://zrok.io)
+* Free, open-source ingress management tools, like [zrok](https://zrok.io)
 
 How you configure your reverse proxy varies based on the system you're using.
 

content/webhooks/using-webhooks/validating-webhook-deliveries.md

@@ -62,7 +62,7 @@ You can use the following `secret` and `payload` values to verify that your impl
 
 If your implementation is correct, the signatures that you generate should match the following signature values:
 
-* signature: `757107ea0eb2509fc211221cce984b8a37570b6d7586c22c46f4379c8b043e17`
+* signature: `757107ea0eb2509fc211221cce984b8a37570b6d7586c22c46f4379c8b043e17` <!-- markdownlint-disable-line GHD034 -->
 * X-Hub-Signature-256: `sha256=757107ea0eb2509fc211221cce984b8a37570b6d7586c22c46f4379c8b043e17`
 
 ### Examples

data/reusables/actions/enable-debug-logging.md

@@ -1,4 +1,2 @@
-{% ifversion debug-reruns %}
 1. Optionally, to enable runner diagnostic logging and step debug logging for the re-run, select **Enable debug logging**.
 1. Click **Re-run jobs**.
-{% endif %}

data/reusables/actions/github-token-scope-descriptions.md

@@ -11,9 +11,7 @@ Available permissions and details of what each allows an action to do:
 |  `checks` | Work with check runs and check suites. For example, `checks: write` permits an action to create a check run. For more information, see [AUTOTITLE](/rest/overview/permissions-required-for-github-apps?apiVersion=2022-11-28#repository-permissions-for-checks). |
 |  `contents` | Work with the contents of the repository. For example, `contents: read` permits an action to list the commits, and `contents: write` allows the action to create a release. For more information, see [AUTOTITLE](/rest/overview/permissions-required-for-github-apps?apiVersion=2022-11-28#repository-permissions-for-contents). |
 |  `deployments` | Work with deployments. For example, `deployments: write` permits an action to create a new deployment. For more information, see [AUTOTITLE](/rest/overview/permissions-required-for-github-apps?apiVersion=2022-11-28#repository-permissions-for-deployments). |
-| {% ifversion discussions %} |
 |  `discussions` | Work with GitHub Discussions. For example, `discussions: write` permits an action to close or delete a discussion. For more information, see [AUTOTITLE](/graphql/guides/using-the-graphql-api-for-discussions). |
-| {% endif %} |
 | {% ifversion fpt or ghec %} |
 |  `id-token` | Fetch an OpenID Connect (OIDC) token. This requires `id-token: write`. For more information, see [AUTOTITLE](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect#updating-your-actions-for-oidc) |
 | {% endif %} |

data/reusables/discussions/marking-a-comment-as-an-answer.md

@@ -4,7 +4,7 @@ When you mark a question as an answer, {% data variables.product.product_name %}
 
 ![Screenshot of a comment marked as the answer to a discussion.](/assets/images/help/discussions/comment-marked-as-answer.png)
 
-{% ifversion discussions-mark-threaded-comment-as-answer %}You can also mark a threaded comment (in response to a comment) as the answer to a discussion. You can't mark a minimized comment as the answer to a discussion. {% else %}You can't mark a threaded comment in response to a comment as the answer to a discussion. You also can't mark a minimized comment as the answer to a discussion.{% endif %}
+You can also mark a threaded comment (in response to a comment) as the answer to a discussion. You can't mark a minimized comment as the answer to a discussion.
 
 {% data reusables.discussions.navigate-to-repo-or-org %}
 {% data reusables.discussions.discussions-tab %}

data/reusables/enterprise_installation/new-instance-attack-vector-warning.md

@@ -1,2 +1,2 @@
 > [!WARNING]
-> To prevent an attacker from compromising the new instance, ensure that you personally set the {% ifversion enterprise-management-console-multi-user-auth %}root {% endif %}{% data variables.enterprise.management_console %} password and create the first user as soon as possible.
+> To prevent an attacker from compromising the new instance, ensure that you personally set the root {% data variables.enterprise.management_console %} password and create the first user as soon as possible.

data/reusables/enterprise_installation/new-instance-config-summary.md

@@ -1 +1 @@
-To configure the instance, you must upload a license file, set the {% ifversion enterprise-management-console-multi-user-auth %}root {% endif %}{% data variables.enterprise.management_console %} password, configure the instance's settings, and restart the instance.
+To configure the instance, you must upload a license file, set the root {% data variables.enterprise.management_console %} password, configure the instance's settings, and restart the instance.

data/reusables/enterprise_management_console/type-management-console-password.md

@@ -1,6 +1,2 @@
-{%- ifversion enterprise-management-console-multi-user-auth %}
 1. If you have created multiple {% data variables.enterprise.management_console %} user accounts, select **Root site admin** or **{% data variables.enterprise.management_console %} user**. For more information about {% data variables.enterprise.management_console %} user accounts see, [AUTOTITLE](/admin/configuration/administering-your-instance-from-the-management-console/managing-access-to-the-management-console).
 1. Type your {% data variables.enterprise.management_console %} credentials. Then click **Continue**.
-{%- else %}
-1. If prompted, type your {% data variables.enterprise.management_console %} password.
-{%- endif %}

data/reusables/enterprise_management_console/unlocking-management-console-with-shell.md

@@ -1 +1 @@
-If the root site administrator's {% data variables.enterprise.management_console %} login is locked, someone with administrative SSH access must unlock the login. To immediately unlock access to the {% data variables.enterprise.management_console %}{% ifversion enterprise-management-console-multi-user-auth %} by the root site administrator{% endif %}, use the `ghe-reactivate-admin-login` command via the administrative shell. For more information, see [AUTOTITLE](/admin/configuration/configuring-your-enterprise/command-line-utilities#ghe-reactivate-admin-login) and [AUTOTITLE](/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh).
+If the root site administrator's {% data variables.enterprise.management_console %} login is locked, someone with administrative SSH access must unlock the login. To immediately unlock access to the {% data variables.enterprise.management_console %} by the root site administrator, use the `ghe-reactivate-admin-login` command via the administrative shell. For more information, see [AUTOTITLE](/admin/configuration/configuring-your-enterprise/command-line-utilities#ghe-reactivate-admin-login) and [AUTOTITLE](/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh).

data/reusables/enterprise_site_admin_settings/management-console-access.md

@@ -2,4 +2,4 @@
 
 {% data reusables.enterprise_site_admin_settings.management-console-overview %} For more information, see [AUTOTITLE](/admin/configuration/administering-your-instance-from-the-management-console/about-the-management-console).
 
-You can access the {% data variables.enterprise.management_console %}{% ifversion enterprise-management-console-multi-user-auth %} as the root site administrator or a {% data variables.enterprise.management_console %} user{% endif %}. An administrator created the {% ifversion enterprise-management-console-multi-user-auth %}root site administrator {% endif %}password during the initial setup process for {% data variables.location.product_location %}.
+You can access the {% data variables.enterprise.management_console %} as the root site administrator or a {% data variables.enterprise.management_console %} user. An administrator created the root site administrator password during the initial setup process for {% data variables.location.product_location %}.

data/reusables/organizations/additional-permissions.md

@@ -1,5 +1,3 @@
-{% ifversion discussions %}
-
 ### Discussions
 
 * Create a discussion category
@@ -10,7 +8,6 @@
 * Convert issues to discussions
 
 For more information, see [AUTOTITLE](/discussions).
-{% endif %}
 
 ### Issue and Pull Requests
 
@@ -50,9 +47,7 @@ For more information, see [AUTOTITLE](/discussions).
 * Create protected tags
 * Delete protected tags
 * Bypass branch protections
-{%- ifversion edit-repository-rules %}
 * Edit repository rules
-{%- endif %}
 
 ### Security
 

data/reusables/pull_requests/required-reviews-for-prs-summary.md

@@ -1 +1 @@
-Repository administrators{% ifversion edit-repository-rules %} or custom roles with the "edit repository rules" permission{% endif %} can require that all pull requests receive a specific number of approving reviews before someone merges the pull request into a protected branch. You can require approving reviews from people with write permissions in the repository or from a designated code owner.
+Repository administrators or custom roles with the "edit repository rules" permission can require that all pull requests receive a specific number of approving reviews before someone merges the pull request into a protected branch. You can require approving reviews from people with write permissions in the repository or from a designated code owner.

data/reusables/repositories/repo-rules-permissions.md

@@ -1 +1 @@
-Anyone with read access to a repository can view the repository's rulesets. People with admin access to a repository{% ifversion edit-repository-rules %}, or a custom role with the "edit repository rules" permission,{% endif %} can create, edit, and delete rulesets for a repository{% ifversion fpt %}.{% else %} and view ruleset insights. For more information, see [AUTOTITLE](/organizations/managing-user-access-to-your-organizations-repositories/managing-repository-roles/about-custom-repository-roles).{% endif %}
+Anyone with read access to a repository can view the repository's rulesets. People with admin access to a repository, or a custom role with the "edit repository rules" permission, can create, edit, and delete rulesets for a repository{% ifversion fpt %}.{% else %} and view ruleset insights. For more information, see [AUTOTITLE](/organizations/managing-user-access-to-your-organizations-repositories/managing-repository-roles/about-custom-repository-roles).{% endif %}

data/reusables/rest-api/about-api-versions.md

@@ -2,23 +2,23 @@ The {% data variables.product.product_name %} REST API is versioned. The API ver
 
 Any breaking changes will be released in a new API version. Breaking changes are changes that can potentially break an integration. Breaking changes include:
 
-* removing an entire operation
+* Removing an entire operation
-* removing or renaming a parameter
+* Removing or renaming a parameter
-* removing or renaming a response field
+* Removing or renaming a response field
-* adding a new required parameter
+* Adding a new required parameter
-* making a previously optional parameter required
+* Making a previously optional parameter required
-* changing the type of a parameter or response field
+* Changing the type of a parameter or response field
-* removing enum values
+* Removing enum values
-* adding a new validation rule to an existing parameter
+* Adding a new validation rule to an existing parameter
-* changing authentication or authorization requirements
+* Changing authentication or authorization requirements
 
 Any additive (non-breaking) changes will be available in all supported API versions. Additive changes are changes that should not break an integration. Additive changes include:
 
-* adding an operation
+* Adding an operation
-* adding an optional parameter
+* Adding an optional parameter
-* adding an optional request header
+* Adding an optional request header
-* adding a response field
+* Adding a response field
-* adding a response header
+* Adding a response header
-* adding enum values
+* Adding enum values
 
 When a new REST API version is released, the previous API version will be supported for at least 24 more months following the release of the new API version.

data/reusables/support/help_resources.md

@@ -1,7 +1,7 @@
 For questions, bug reports, and discussions about {% data variables.product.prodname_github_apps %}, {% data variables.product.prodname_oauth_apps %}, and API development, explore the {% data reusables.support.prodname_support_forum_with_url %}. The discussions are moderated and maintained by {% data variables.product.company_short %} staff, and answered by the {% data variables.product.company_short %} community.
 
 Consider reaching out to [GitHub Support](https://support.github.com/) directly using the contact form for:
-* guaranteed response from {% data variables.product.product_name %} staff
+* Guaranteed response from {% data variables.product.product_name %} staff
-* support requests involving sensitive data or private concerns
+* Support requests involving sensitive data or private concerns
-* feature requests
+* Feature requests
-* feedback about {% data variables.product.product_name %} products
+* Feedback about {% data variables.product.product_name %} products