github · docs-bot · Jan 16, 2025 · Jan 16, 2025 · Jan 16, 2025 · Jan 16, 2025
diff --git a/...ow-runs-and-deployments/managing-workflow-runs/re-running-workflows-and-jobs.md b/...ow-runs-and-deployments/managing-workflow-runs/re-running-workflows-and-jobs.md
@@ -1,7 +1,7 @@
 ---
 title: Re-running workflows and jobs
 shortTitle: Re-run workflows and jobs
 intro: 'You can re-run a workflow run{% ifversion re-run-jobs %}, all failed jobs in a workflow run, or specific jobs in a workflow run{% endif %} up to 30 days after its initial run.'
 permissions: People with write permissions to a repository can re-run workflows in the repository.
 redirect_from:
  - /actions/managing-workflow-runs/re-running-a-workflow
@@ -16,7 +16,7 @@
 
 ## 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 @@
 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
@@ -63,7 +60,7 @@

 {% endcli %}

 {% ifversion re-run-jobs %}

 ## Re-running failed jobs in a workflow

@@ -88,14 +85,12 @@
 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,19 +117,17 @@
 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 %}

 {% ifversion partial-reruns-with-reusable %}

 ## Re-running workflows and jobs with reusable workflows

@@ -150,7 +143,7 @@
 {% data reusables.repositories.actions-tab %}
 {% data reusables.repositories.navigate-to-workflow %}
 {% data reusables.repositories.view-run %}
 {%- ifversion re-run-jobs %}
 1. To the right of the run name, select the **Latest** dropdown menu and click a previous run attempt.
 {%- else %}
 1. In the left pane, click a previous run attempt.

diff --git a/...d-troubleshooting-workflows/troubleshooting-workflows/enabling-debug-logging.md b/...d-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:

diff --git a/...nce/administering-your-instance-from-the-command-line/command-line-utilities.md b/...nce/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

diff --git a/...nce/administering-your-instance-from-the-web-ui/about-the-management-console.md b/...nce/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.

diff --git a/...ring-your-instance-from-the-web-ui/managing-access-to-the-management-console.md b/...ring-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 %}
diff --git a/...ur-instance-from-the-web-ui/troubleshooting-access-to-the-management-console.md b/...ur-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 %}
-
-{% ifversion enterprise-management-console-multi-user-auth %}
+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).
 
 ### 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.

diff --git a/...migrating-your-enterprise-to-the-container-registry-from-the-docker-registry.md b/...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

diff --git a/...thub-enterprise-server-instance/installing-github-enterprise-server-on-azure.md b/...thub-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 %}
 

diff --git a/...on-to-users-in-your-enterprise/customizing-user-messages-for-your-enterprise.md b/...on-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 %}