diff --git a/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md b/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md index 44a98f50367d..fc0855812d24 100644 --- a/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md +++ b/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md @@ -96,11 +96,11 @@ For a longer-form and more prominent way of displaying customized information ab {% data reusables.user-settings.access_settings %} 1. Under "Public profile", in the "Bio" field, type the content that you want displayed on your profile. The bio field is limited to 160 characters. - {% tip %} + {% tip %} - **Tip:** When you @mention an organization, only those that you're a member of will autocomplete. You can still @mention organizations that you're not a member of, like a previous employer, but the organization name won't autocomplete for you. + **Tip:** When you @mention an organization, only those that you're a member of will autocomplete. You can still @mention organizations that you're not a member of, like a previous employer, but the organization name won't autocomplete for you. - {% endtip %} + {% endtip %} {% data reusables.profile.update-profile %} diff --git a/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/managing-multiple-accounts.md b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/managing-multiple-accounts.md index bedb4e34e4de..1df8889360a7 100644 --- a/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/managing-multiple-accounts.md +++ b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/managing-multiple-accounts.md @@ -54,9 +54,9 @@ Alternatively, if you want to use the HTTPS protocol for both accounts, you can {% data reusables.git.clear-stored-gcm-credentials %} - ```shell copy - echo "protocol=https\nhost=github.com" | git credential-manager erase - ``` + ```shell copy + echo "protocol=https\nhost=github.com" | git credential-manager erase + ``` {% data reusables.git.cache-on-repository-path %} {% data reusables.accounts.create-personal-access-tokens %} {% data reusables.git.provide-credentials %} diff --git a/content/actions/creating-actions/creating-a-composite-action.md b/content/actions/creating-actions/creating-a-composite-action.md index 4fd4f17ee793..902f72affd8b 100644 --- a/content/actions/creating-actions/creating-a-composite-action.md +++ b/content/actions/creating-actions/creating-a-composite-action.md @@ -13,7 +13,7 @@ type: tutorial topics: - Action development --- - + {% data reusables.actions.enterprise-github-hosted-runners %} ## Introduction @@ -95,11 +95,11 @@ Before you begin, you'll create a repository on {% ifversion ghae %}{% data vari shell: bash ``` {% endraw %} - This file defines the `who-to-greet` input, maps the random generated number to the `random-number` output variable, adds the action's path to the runner system path (to locate the `goodbye.sh` script during execution), and runs the `goodbye.sh` script. + This file defines the `who-to-greet` input, maps the random generated number to the `random-number` output variable, adds the action's path to the runner system path (to locate the `goodbye.sh` script during execution), and runs the `goodbye.sh` script. - For more information about managing outputs, see "[AUTOTITLE](/actions/creating-actions/metadata-syntax-for-github-actions#outputs-for-composite-actions)". + For more information about managing outputs, see "[AUTOTITLE](/actions/creating-actions/metadata-syntax-for-github-actions#outputs-for-composite-actions)". - For more information about how to use `github.action_path`, see "[AUTOTITLE](/actions/learn-github-actions/contexts#github-context)". + For more information about how to use `github.action_path`, see "[AUTOTITLE](/actions/learn-github-actions/contexts#github-context)". 1. From your terminal, check in your `action.yml` file. diff --git a/content/actions/hosting-your-own-runners/managing-self-hosted-runners/monitoring-and-troubleshooting-self-hosted-runners.md b/content/actions/hosting-your-own-runners/managing-self-hosted-runners/monitoring-and-troubleshooting-self-hosted-runners.md index adbf94174b9a..1ab0952ea7f7 100644 --- a/content/actions/hosting-your-own-runners/managing-self-hosted-runners/monitoring-and-troubleshooting-self-hosted-runners.md +++ b/content/actions/hosting-your-own-runners/managing-self-hosted-runners/monitoring-and-troubleshooting-self-hosted-runners.md @@ -15,7 +15,7 @@ type: tutorial defaultPlatform: linux shortTitle: Monitor & troubleshoot --- - + {% data reusables.actions.enterprise-github-hosted-runners %} {% ifversion actions-disable-repo-runners %} @@ -101,13 +101,13 @@ export GITHUB_ACTIONS_RUNNER_TLS_NO_VERIFY=1 ## Reviewing the self-hosted runner application log files -You can monitor the status of the self-hosted runner application and its activities. Log files are kept in the `_diag` directory where you installed the runner application, and a new log is generated each time the application is started. The filename begins with _Runner__, and is followed by a UTC timestamp of when the application was started. +You can monitor the status of the self-hosted runner application and its activities. Log files are kept in the `_diag` directory where you installed the runner application, and a new log is generated each time the application is started. The filename begins with \_Runner__, and is followed by a UTC timestamp of when the application was started. -For detailed logs on workflow job executions, see the next section describing the _Worker__ files. +For detailed logs on workflow job executions, see the next section describing the \_Worker__ files. ## Reviewing a job's log file -The self-hosted runner application creates a detailed log file for each job that it processes. These files are stored in the `_diag` directory where you installed the runner application, and the filename begins with _Worker__. +The self-hosted runner application creates a detailed log file for each job that it processes. These files are stored in the `_diag` directory where you installed the runner application, and the filename begins with \_Worker__. {% linux %} @@ -221,7 +221,7 @@ PS C:\actions-runner> Get-EventLog -LogName Application -Source ActionsRunnerSer We recommend that you regularly check the automatic update process, as the self-hosted runner will not be able to process jobs if it falls below a certain version threshold. The self-hosted runner application automatically updates itself, but note that this process does not include any updates to the operating system or other software; you will need to separately manage these updates. -You can view the update activities in the _Runner__ log files. For example: +You can view the update activities in the \_Runner__ log files. For example: ```shell [Feb 12 12:37:07 INFO SelfUpdater] An update is available. diff --git a/data/reusables/actions/self-hosted-runner-auto-removal.md b/data/reusables/actions/self-hosted-runner-auto-removal.md index 4c469b3061fc..63530de4f05a 100644 --- a/data/reusables/actions/self-hosted-runner-auto-removal.md +++ b/data/reusables/actions/self-hosted-runner-auto-removal.md @@ -1,6 +1,4 @@ -{% ifversion fpt or ghec or ghes > 3.6 %} -A self-hosted runner is automatically removed from {% data variables.product.product_name %} if it has not connected to {% data variables.product.prodname_actions %} for more than 14 days. An ephemeral self-hosted runner is automatically removed from {% data variables.product.product_name %} if it has not connected to {% data variables.product.prodname_actions %} for more than 1 day. +{% ifversion fpt or ghec or ghes > 3.6 %}A self-hosted runner is automatically removed from {% data variables.product.product_name %} if it has not connected to {% data variables.product.prodname_actions %} for more than 14 days. An ephemeral self-hosted runner is automatically removed from {% data variables.product.product_name %} if it has not connected to {% data variables.product.prodname_actions %} for more than 1 day. -{% elsif ghae or ghes < 3.7 %} -A self-hosted runner is automatically removed from {% data variables.product.product_name %} if it has not connected to {% data variables.product.prodname_actions %} for more than 30 days. +{% elsif ghae or ghes < 3.7 %}A self-hosted runner is automatically removed from {% data variables.product.product_name %} if it has not connected to {% data variables.product.prodname_actions %} for more than 30 days. {% endif %}