diff --git a/data/reusables/accounts/accounts-billed-separately.md b/data/reusables/accounts/accounts-billed-separately.md index 9e417e9ed1b1..d2d569abb6df 100644 --- a/data/reusables/accounts/accounts-billed-separately.md +++ b/data/reusables/accounts/accounts-billed-separately.md @@ -1 +1 @@ -Each account on {% data variables.product.product_name %} is billed separately. Upgrading an organization account enables paid features for the organization's repositories only and does not affect the features available in repositories owned by any associated personal accounts. Similarly, upgrading a personal account enables paid features for the personal account's repositories only and does not affect the repositories of any organization accounts. For more information about account types, see [AUTOTITLE](/get-started/learning-about-github/types-of-github-accounts). +Each account on {% data variables.product.github %} is billed separately. Upgrading an organization account enables paid features for the organization's repositories only and does not affect the features available in repositories owned by any associated personal accounts. Similarly, upgrading a personal account enables paid features for the personal account's repositories only and does not affect the repositories of any organization accounts. For more information about account types, see [AUTOTITLE](/get-started/learning-about-github/types-of-github-accounts). diff --git a/data/reusables/accounts/marketing-emails.md b/data/reusables/accounts/marketing-emails.md index 4f4e0ba208c8..1eb34c57d143 100644 --- a/data/reusables/accounts/marketing-emails.md +++ b/data/reusables/accounts/marketing-emails.md @@ -1,4 +1,4 @@ -{% data variables.product.product_name %} occasionally sends the following types of marketing emails: +{% data variables.product.github %} occasionally sends the following types of marketing emails: * Tips and tricks for getting started with your account * Customized information about engaging projects or new features diff --git a/data/reusables/actions/about-triggers.md b/data/reusables/actions/about-triggers.md index f4946cd226f1..ff95af94a641 100644 --- a/data/reusables/actions/about-triggers.md +++ b/data/reusables/actions/about-triggers.md @@ -1,7 +1,7 @@ Workflow triggers are events that cause a workflow to run. These events can be: * Events that occur in your workflow's repository -* Events that occur outside of {% data variables.product.product_name %} and trigger a `repository_dispatch` event on {% data variables.product.product_name %} +* Events that occur outside of {% data variables.product.github %} and trigger a `repository_dispatch` event on {% data variables.product.github %} * Scheduled times * Manual diff --git a/data/reusables/actions/actions-bundled-with-ghes.md b/data/reusables/actions/actions-bundled-with-ghes.md index be390efc03e5..3bf2b859b47e 100644 --- a/data/reusables/actions/actions-bundled-with-ghes.md +++ b/data/reusables/actions/actions-bundled-with-ghes.md @@ -1 +1 @@ -Most official {% data variables.product.prodname_dotcom %}-authored actions are automatically bundled with {% data variables.product.product_name %}, and are captured at a point in time from {% data variables.product.prodname_marketplace %}. +Most official {% data variables.product.github %}-authored actions are automatically bundled with {% data variables.product.prodname_ghe_server %}, and are captured at a point in time from {% data variables.product.prodname_marketplace %}. diff --git a/data/reusables/actions/artifact-log-retention-statement.md b/data/reusables/actions/artifact-log-retention-statement.md index 65c0f8236f82..7e960b3939da 100644 --- a/data/reusables/actions/artifact-log-retention-statement.md +++ b/data/reusables/actions/artifact-log-retention-statement.md @@ -1 +1 @@ -By default, {% data variables.product.product_name %} stores build logs and artifacts for 90 days, and this retention period can be customized. For more information, see [AUTOTITLE](/actions/learn-github-actions/usage-limits-billing-and-administration#artifact-and-log-retention-policy). +By default, {% data variables.product.github %} stores build logs and artifacts for 90 days, and this retention period can be customized. For more information, see [AUTOTITLE](/actions/learn-github-actions/usage-limits-billing-and-administration#artifact-and-log-retention-policy). diff --git a/data/reusables/actions/azure-vnet-procedures-prereqs.md b/data/reusables/actions/azure-vnet-procedures-prereqs.md index 209909becde6..2b3eef76f0f1 100644 --- a/data/reusables/actions/azure-vnet-procedures-prereqs.md +++ b/data/reusables/actions/azure-vnet-procedures-prereqs.md @@ -15,7 +15,7 @@ You will use a script to automate configuring your Azure resources. If you use {% data variables.enterprise.data_residency %}, in the `AllowOutBoundGitHub` section, you must also include the egress IP ranges for {% data variables.enterprise.data_residency_site %}. See [AUTOTITLE](/admin/data-residency/network-details-for-ghecom#ranges-for-egress-traffic). > [!NOTE] - > As an alternative to using the following file, to allow {% data variables.product.prodname_actions %} to communicate with the runners, you can allow the same firewall domains that are required for communication between self-hosted runners and {% data variables.product.product_name %}. For more information, see [AUTOTITLE](/actions/hosting-your-own-runners/managing-self-hosted-runners/about-self-hosted-runners#communication-between-self-hosted-runners-and-github-enterprise-cloud). To determine the appropriate subnet IP address range, we recommend adding a 30% buffer to the maximum job concurrency you anticipate. For instance, if your network configuration's runners are set to a maximum job concurrency of 300, it's recommended to utilize a subnet IP address range that can accommodate at least 390 runners. This buffer helps ensure that your network can handle unexpected increases in VM needs to meet job concurrency without running out of IP addresses. + > As an alternative to using the following file, to allow {% data variables.product.prodname_actions %} to communicate with the runners, you can allow the same firewall domains that are required for communication between self-hosted runners and {% data variables.product.github %}. For more information, see [AUTOTITLE](/actions/hosting-your-own-runners/managing-self-hosted-runners/about-self-hosted-runners#communication-between-self-hosted-runners-and-github-enterprise-cloud). To determine the appropriate subnet IP address range, we recommend adding a 30% buffer to the maximum job concurrency you anticipate. For instance, if your network configuration's runners are set to a maximum job concurrency of 300, it's recommended to utilize a subnet IP address range that can accommodate at least 390 runners. This buffer helps ensure that your network can handle unexpected increases in VM needs to meet job concurrency without running out of IP addresses. ```bicep copy @description('NSG for outbound rules') diff --git a/data/reusables/actions/cd-templates-actions.md b/data/reusables/actions/cd-templates-actions.md index db3b02b47783..3d87171dcaa9 100644 --- a/data/reusables/actions/cd-templates-actions.md +++ b/data/reusables/actions/cd-templates-actions.md @@ -1,3 +1,3 @@ -{% data variables.product.product_name %} offers deployment workflow templates for several popular services, such as Azure Web App. To learn how to get started using a workflow template, see [AUTOTITLE](/actions/learn-github-actions/using-starter-workflows) or [browse the full list of deployment workflow templates](https://github.com/actions/starter-workflows/tree/main/deployments). You can also check out our more detailed guides for specific deployment workflows, such as [AUTOTITLE](/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-nodejs-to-azure-app-service). +{% data variables.product.github %} offers deployment workflow templates for several popular services, such as Azure Web App. To learn how to get started using a workflow template, see [AUTOTITLE](/actions/learn-github-actions/using-starter-workflows) or [browse the full list of deployment workflow templates](https://github.com/actions/starter-workflows/tree/main/deployments). You can also check out our more detailed guides for specific deployment workflows, such as [AUTOTITLE](/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-nodejs-to-azure-app-service). Many service providers also offer actions on {% data variables.product.prodname_marketplace %} for deploying to their service. For the full list, see [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?category=deployment&type=actions). diff --git a/data/reusables/actions/disable-selfhosted-runners-overview.md b/data/reusables/actions/disable-selfhosted-runners-overview.md index ac977c324725..6e20be2c7f74 100644 --- a/data/reusables/actions/disable-selfhosted-runners-overview.md +++ b/data/reusables/actions/disable-selfhosted-runners-overview.md @@ -1,4 +1,4 @@ -There is no guarantee that self-hosted runners for {% data variables.product.product_name %} will be hosted on ephemeral, clean virtual machines. As a result, they may be compromised by untrusted code in a workflow. +There is no guarantee that self-hosted runners for {% data variables.product.github %} will be hosted on ephemeral, clean virtual machines. As a result, they may be compromised by untrusted code in a workflow. Similarly, anyone who can fork the repository and open a pull request (generally those with read access to the repository) can compromise the self-hosted runner environment, including gaining access to secrets and the `GITHUB_TOKEN` which, depending on its settings, can grant write access to the repository. Although workflows can control access to environment secrets by using environments and required reviews, these workflows are not run in an isolated environment and are still susceptible to the same risks when run on a self-hosted runner. diff --git a/data/reusables/actions/enterprise-no-internet-actions.md b/data/reusables/actions/enterprise-no-internet-actions.md index e568edbd056b..62188dbc9b95 100644 --- a/data/reusables/actions/enterprise-no-internet-actions.md +++ b/data/reusables/actions/enterprise-no-internet-actions.md @@ -1 +1 @@ -{% data variables.product.prodname_actions %} on {% data variables.product.product_name %} is designed to work in environments without full internet access. By default, workflows cannot use actions from {% data variables.product.prodname_dotcom_the_website %} and [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions). +{% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %} is designed to work in environments without full internet access. By default, workflows cannot use actions from {% data variables.product.prodname_dotcom_the_website %} and [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions). diff --git a/data/reusables/actions/gai-inspect-pull-request.md b/data/reusables/actions/gai-inspect-pull-request.md index 916a7b79e151..413bddcbdd17 100644 --- a/data/reusables/actions/gai-inspect-pull-request.md +++ b/data/reusables/actions/gai-inspect-pull-request.md @@ -5,6 +5,6 @@ The output from a successful run of the `migrate` command contains a link to the Some important elements of the pull request include: * In the pull request description, a section called **Manual steps**, which lists steps that you must manually complete before you can finish migrating your pipelines to {% data variables.product.prodname_actions %}. For example, this section might tell you to create any secrets used in your workflows. -* The converted workflows file. Select the **Files changed** tab in the pull request to view the workflow file that will be added to your {% data variables.product.product_name %} repository. +* The converted workflows file. Select the **Files changed** tab in the pull request to view the workflow file that will be added to your {% data variables.product.github %} repository. -When you are finished inspecting the pull request, you can merge it to add the workflow to your {% data variables.product.product_name %} repository. +When you are finished inspecting the pull request, you can merge it to add the workflow to your {% data variables.product.github %} repository. diff --git a/data/reusables/actions/jobs/section-using-a-build-matrix-for-your-jobs-failfast.md b/data/reusables/actions/jobs/section-using-a-build-matrix-for-your-jobs-failfast.md index 0cef62d32ad4..154fc6334a10 100644 --- a/data/reusables/actions/jobs/section-using-a-build-matrix-for-your-jobs-failfast.md +++ b/data/reusables/actions/jobs/section-using-a-build-matrix-for-your-jobs-failfast.md @@ -1,6 +1,6 @@ You can control how job failures are handled with `jobs..strategy.fail-fast` and `jobs..continue-on-error`. -`jobs..strategy.fail-fast` applies to the entire matrix. If `jobs..strategy.fail-fast` is set to `true` or its expression evaluates to `true`, {% data variables.product.product_name %} will cancel all in-progress and queued jobs in the matrix if any job in the matrix fails. This property defaults to `true`. +`jobs..strategy.fail-fast` applies to the entire matrix. If `jobs..strategy.fail-fast` is set to `true` or its expression evaluates to `true`, {% data variables.product.github %} will cancel all in-progress and queued jobs in the matrix if any job in the matrix fails. This property defaults to `true`. `jobs..continue-on-error` applies to a single job. If `jobs..continue-on-error` is `true`, other jobs in the matrix will continue running even if the job with `jobs..continue-on-error: true` fails. diff --git a/data/reusables/actions/jobs/section-using-a-build-matrix-for-your-jobs-max-parallel.md b/data/reusables/actions/jobs/section-using-a-build-matrix-for-your-jobs-max-parallel.md index fd58b0c321b1..12de48bc5caf 100644 --- a/data/reusables/actions/jobs/section-using-a-build-matrix-for-your-jobs-max-parallel.md +++ b/data/reusables/actions/jobs/section-using-a-build-matrix-for-your-jobs-max-parallel.md @@ -1,4 +1,4 @@ -By default, {% data variables.product.product_name %} will maximize the number of jobs run in parallel depending on runner availability. To set the maximum number of jobs that can run simultaneously when using a `matrix` job strategy, use `jobs..strategy.max-parallel`. +By default, {% data variables.product.github %} will maximize the number of jobs run in parallel depending on runner availability. To set the maximum number of jobs that can run simultaneously when using a `matrix` job strategy, use `jobs..strategy.max-parallel`. For example, the following workflow will run a maximum of two jobs at a time, even if there are runners available to run all six jobs at once. diff --git a/data/reusables/actions/jobs/section-using-jobs-in-a-workflow.md b/data/reusables/actions/jobs/section-using-jobs-in-a-workflow.md index 6fc377b96374..229759637fc2 100644 --- a/data/reusables/actions/jobs/section-using-jobs-in-a-workflow.md +++ b/data/reusables/actions/jobs/section-using-jobs-in-a-workflow.md @@ -4,4 +4,4 @@ Each job runs in a runner environment specified by `runs-on`. You can run an unlimited number of jobs as long as you are within the workflow usage limits. For more information, see [AUTOTITLE](/actions/learn-github-actions/usage-limits-billing-and-administration) for {% data variables.product.prodname_dotcom %}-hosted runners and [AUTOTITLE](/actions/hosting-your-own-runners/managing-self-hosted-runners/about-self-hosted-runners#usage-limits) for self-hosted runner usage limits. -If you need to find the unique identifier of a job running in a workflow run, you can use the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API. For more information, see [AUTOTITLE](/rest/actions#workflow-jobs). +If you need to find the unique identifier of a job running in a workflow run, you can use the {% data variables.product.github %} API. For more information, see [AUTOTITLE](/rest/actions#workflow-jobs). diff --git a/data/reusables/actions/jobs/using-matrix-strategy.md b/data/reusables/actions/jobs/using-matrix-strategy.md index de7dd27df5e4..10f2f6ee1ea4 100644 --- a/data/reusables/actions/jobs/using-matrix-strategy.md +++ b/data/reusables/actions/jobs/using-matrix-strategy.md @@ -11,7 +11,7 @@ jobs: A job will run for each possible combination of the variables. In this example, the workflow will run six jobs, one for each combination of the `os` and `version` variables. -By default, {% data variables.product.product_name %} will maximize the number of jobs run in parallel depending on runner availability. The order of the variables in the matrix determines the order in which the jobs are created. The first variable you define will be the first job that is created in your workflow run. For example, the above matrix will create the jobs in the following order: +By default, {% data variables.product.github %} will maximize the number of jobs run in parallel depending on runner availability. The order of the variables in the matrix determines the order in which the jobs are created. The first variable you define will be the first job that is created in your workflow run. For example, the above matrix will create the jobs in the following order: * `{version: 10, os: ubuntu-latest}` * `{version: 10, os: windows-latest}` @@ -20,6 +20,6 @@ By default, {% data variables.product.product_name %} will maximize the number o * `{version: 14, os: ubuntu-latest}` * `{version: 14, os: windows-latest}` -A matrix will generate a maximum of 256 jobs per workflow run. This limit applies to both {% data variables.product.product_name %}-hosted and self-hosted runners. +A matrix will generate a maximum of 256 jobs per workflow run. This limit applies to both {% data variables.product.github %}-hosted and self-hosted runners. The variables that you define become properties in the `matrix` context, and you can reference the property in other areas of your workflow file. In this example, you can use `matrix.version` and `matrix.os` to access the current value of `version` and `os` that the job is using. For more information, see [AUTOTITLE](/actions/learn-github-actions/contexts). diff --git a/data/reusables/actions/self-hosted-runner-architecture.md b/data/reusables/actions/self-hosted-runner-architecture.md index e8666a5987e4..68f22ab0e881 100644 --- a/data/reusables/actions/self-hosted-runner-architecture.md +++ b/data/reusables/actions/self-hosted-runner-architecture.md @@ -1 +1 @@ -Your runner machine connects to {% data variables.product.product_name %} using the {% data variables.product.prodname_actions %} self-hosted runner application. +Your runner machine connects to {% data variables.product.github %} using the {% data variables.product.prodname_actions %} self-hosted runner application. diff --git a/data/reusables/actions/self-hosted-runner-auto-removal.md b/data/reusables/actions/self-hosted-runner-auto-removal.md index bf6ae0542846..3b5de2d599ae 100644 --- a/data/reusables/actions/self-hosted-runner-auto-removal.md +++ b/data/reusables/actions/self-hosted-runner-auto-removal.md @@ -1 +1 @@ -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. +A self-hosted runner is automatically removed from {% data variables.product.github %} 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.github %} if it has not connected to {% data variables.product.prodname_actions %} for more than 1 day. diff --git a/data/reusables/actions/self-hosted-runner-check-installation-success.md b/data/reusables/actions/self-hosted-runner-check-installation-success.md index 9da1dd93a08b..abd27759f992 100644 --- a/data/reusables/actions/self-hosted-runner-check-installation-success.md +++ b/data/reusables/actions/self-hosted-runner-check-installation-success.md @@ -3,6 +3,6 @@ After completing the steps to add a self-hosted runner, the runner and its status are now listed under {% ifversion fpt or ghec %}"Runners"{% elsif ghes %}"Self-hosted runners"{% endif %}. -The self-hosted runner application must be active for the runner to accept jobs. When the runner application is connected to {% data variables.product.product_name %} and ready to receive jobs, you will see the following message on the machine's terminal. +The self-hosted runner application must be active for the runner to accept jobs. When the runner application is connected to {% data variables.product.github %} and ready to receive jobs, you will see the following message on the machine's terminal. {% data reusables.actions.self-hosted-runner-connected-output %} diff --git a/data/reusables/actions/self-hosted-runner-ports-protocols.md b/data/reusables/actions/self-hosted-runner-ports-protocols.md index cf0ca083fb00..cc3e336f1572 100644 --- a/data/reusables/actions/self-hosted-runner-ports-protocols.md +++ b/data/reusables/actions/self-hosted-runner-ports-protocols.md @@ -1 +1 @@ -The connection between self-hosted runners and {% data variables.product.product_name %} is over {% ifversion ghes %}HTTP (port 80) or {% endif %}HTTPS (port 443). {% ifversion ghes %}To ensure connectivity over HTTPS, configure TLS for {% data variables.product.prodname_ghe_server %}. For more information, see [AUTOTITLE](/admin/configuration/hardening-security-for-your-enterprise/configuring-tls).{% endif %} +The connection between self-hosted runners and {% data variables.product.github %} is over {% ifversion ghes %}HTTP (port 80) or {% endif %}HTTPS (port 443). {% ifversion ghes %}To ensure connectivity over HTTPS, configure TLS for {% data variables.product.prodname_ghe_server %}. For more information, see [AUTOTITLE](/admin/configuration/hardening-security-for-your-enterprise/configuring-tls).{% endif %} diff --git a/data/reusables/actions/self-hosted-runner-removing-a-runner-updated.md b/data/reusables/actions/self-hosted-runner-removing-a-runner-updated.md index fca17414e944..59c75f680b3f 100644 --- a/data/reusables/actions/self-hosted-runner-removing-a-runner-updated.md +++ b/data/reusables/actions/self-hosted-runner-removing-a-runner-updated.md @@ -5,8 +5,8 @@ The removal command does the following tasks: - * Removes the runner from {% data variables.product.product_name %}. + * Removes the runner from {% data variables.product.github %}. * Removes any self-hosted runner application configuration files on the machine. * Removes any services configured if not running in interactive mode. - * **If you don't have access to the machine:** Click **Force remove this runner** to force {% data variables.product.product_name %} to remove the runner. + * **If you don't have access to the machine:** Click **Force remove this runner** to force {% data variables.product.github %} to remove the runner. diff --git a/data/reusables/actions/self-hosted-runner-reusing.md b/data/reusables/actions/self-hosted-runner-reusing.md index fc4385231b71..a9ce6a05ba0c 100644 --- a/data/reusables/actions/self-hosted-runner-reusing.md +++ b/data/reusables/actions/self-hosted-runner-reusing.md @@ -1 +1 @@ -Alternatively, if you don't have access to the repository{% ifversion fpt %} or organization{% elsif ghes or ghec %}, organization, or enterprise{% endif %} on {% data variables.product.product_name %} to remove a runner, but you would like to re-use the runner machine, then you can delete the `.runner` file inside the self-hosted runner application directory (that is, the directory into which you downloaded and unpacked the runner software). This allows the runner to be registered without having to re-download the self-hosted runner application. +Alternatively, if you don't have access to the repository{% ifversion fpt %} or organization{% elsif ghes or ghec %}, organization, or enterprise{% endif %} on {% data variables.product.github %} to remove a runner, but you would like to re-use the runner machine, then you can delete the `.runner` file inside the self-hosted runner application directory (that is, the directory into which you downloaded and unpacked the runner software). This allows the runner to be registered without having to re-download the self-hosted runner application. diff --git a/data/reusables/actions/self-hosted-runners-prerequisites.md b/data/reusables/actions/self-hosted-runners-prerequisites.md index e9d74bcecfb4..4c8d5270839b 100644 --- a/data/reusables/actions/self-hosted-runners-prerequisites.md +++ b/data/reusables/actions/self-hosted-runners-prerequisites.md @@ -1,5 +1,5 @@ {%- ifversion ghes %} -* {% data variables.product.prodname_actions %} must be enabled for {% data variables.product.product_name %}. A site administrator can enable and configure {% data variables.product.prodname_actions %} for your instance. For more information, see [AUTOTITLE](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server). +* {% data variables.product.prodname_actions %} must be enabled for {% data variables.product.prodname_ghe_server %}. A site administrator can enable and configure {% data variables.product.prodname_actions %} for your instance. For more information, see [AUTOTITLE](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server). {%- endif %} * You must have access to the machine you will use as a self-hosted runner in your environment. diff --git a/data/reusables/actions/usage-matrix-limits.md b/data/reusables/actions/usage-matrix-limits.md index df908885436a..916e9478a08f 100644 --- a/data/reusables/actions/usage-matrix-limits.md +++ b/data/reusables/actions/usage-matrix-limits.md @@ -1 +1 @@ -A job matrix can generate a maximum of 256 jobs per workflow run. This limit applies to both {% data variables.product.product_name %}-hosted and self-hosted runners. +A job matrix can generate a maximum of 256 jobs per workflow run. This limit applies to both {% data variables.product.github %}-hosted and self-hosted runners. diff --git a/data/reusables/actions/workflow-template-overview.md b/data/reusables/actions/workflow-template-overview.md index 103d3ab0bfff..69d6946f7f44 100644 --- a/data/reusables/actions/workflow-template-overview.md +++ b/data/reusables/actions/workflow-template-overview.md @@ -1,4 +1,4 @@ -{% data variables.product.prodname_dotcom %} provides preconfigured workflow templates that you can use as-is or customize to create your own workflow. {% data variables.product.product_name %} analyzes your code and shows you workflow templates that might be useful for your repository. For example, if your repository contains Node.js code, you'll see suggestions for Node.js projects. +{% data variables.product.github %} provides preconfigured workflow templates that you can use as-is or customize to create your own workflow. {% data variables.product.github %} analyzes your code and shows you workflow templates that might be useful for your repository. For example, if your repository contains Node.js code, you'll see suggestions for Node.js projects. These workflow templates are designed to help you get up and running quickly, offering a range of configurations such as: * CI: [Continuous Integration workflows](https://github.com/actions/starter-workflows/tree/main/ci) diff --git a/data/reusables/actions/workflows/required-workflow-prerequisites.md b/data/reusables/actions/workflows/required-workflow-prerequisites.md index a23a793e0c64..bfce75a07a0b 100644 --- a/data/reusables/actions/workflows/required-workflow-prerequisites.md +++ b/data/reusables/actions/workflows/required-workflow-prerequisites.md @@ -1,7 +1,7 @@ * {% data variables.product.prodname_actions %} must be enabled for a repository in the organization's settings in order for required workflows to run. Once enabled at an organization-level, required workflows will run even when {% data variables.product.prodname_actions %} is disabled in the repository's settings. For more information on managing {% data variables.product.prodname_actions %} in your organization's repositories, see [AUTOTITLE](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#managing-github-actions-permissions-for-your-organization). * Required workflows are available for organizations and only in repositories where the organization's plan supports required status checks. If required status checks are not supported, the workflow will still run, but it will not be a required check and will not block merging. For more information about support for required status checks, see [AUTOTITLE](/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/about-protected-branches). * The repository's default branch must match the organization's default branch setting in order for required workflows to run as required status checks. If the default branch names do not match, the workflow will still run, but it will not be a required check. For more information about managing default branch names, see [AUTOTITLE](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization) and [AUTOTITLE](/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/changing-the-default-branch). -* For required workflows to run, the pull request's source repository must be in the same organization as the target repository. {% data variables.product.product_name %} will source the required workflow from a specified branch, tag, or commit SHA from the repository containing the workflow. +* For required workflows to run, the pull request's source repository must be in the same organization as the target repository. {% data variables.product.github %} will source the required workflow from a specified branch, tag, or commit SHA from the repository containing the workflow. * Secrets used in a required workflow should be created at either the organization level or in the target repositories. * Secrets in the source repository will not be fetched when a workflow runs in the target repository. * When a workflow is run as a required workflow it will ignore all the filters in the `on:` section, for example: `branches`, `branches-ignore`, `paths`, `types` etc. The required workflow will run only for the `pull_request` and `pull_request_target` default events. For more information on default activity types, see [AUTOTITLE](/actions/using-workflows/events-that-trigger-workflows#pull_request). diff --git a/data/reusables/apps/ip-allow-list-only-apps.md b/data/reusables/apps/ip-allow-list-only-apps.md index 499e2c7119db..6fb051ad5fae 100644 --- a/data/reusables/apps/ip-allow-list-only-apps.md +++ b/data/reusables/apps/ip-allow-list-only-apps.md @@ -1,2 +1,2 @@ > [!NOTE] -> The addresses in the IP allow list of a {% data variables.product.prodname_github_app %} only affect requests made by installations of the {% data variables.product.prodname_github_app %}. The automatic addition of a {% data variables.product.prodname_github_app %}'s IP address to an organization's allow list does not allow access to a {% data variables.product.product_name %} user who connects from that IP address. +> The addresses in the IP allow list of a {% data variables.product.prodname_github_app %} only affect requests made by installations of the {% data variables.product.prodname_github_app %}. The automatic addition of a {% data variables.product.prodname_github_app %}'s IP address to an organization's allow list does not allow access to a {% data variables.product.github %} user who connects from that IP address. diff --git a/data/reusables/audit_log/audit-log-search-by-user.md b/data/reusables/audit_log/audit-log-search-by-user.md index cf6eeec49649..f0775c31c981 100644 --- a/data/reusables/audit_log/audit-log-search-by-user.md +++ b/data/reusables/audit_log/audit-log-search-by-user.md @@ -6,4 +6,4 @@ The `actor` qualifier can scope events based on who performed the action. For ex * `actor:octocat actor:hubot` finds all events performed by `octocat` or `hubot`. * `-actor:hubot` excludes all events performed by `hubot`. -Note that you can only use a {% data variables.product.product_name %} username, not an individual's real name. +Note that you can only use a {% data variables.product.github %} username, not an individual's real name. diff --git a/data/reusables/audit_log/audit-log-search.md b/data/reusables/audit_log/audit-log-search.md index c4a0fbac3ab2..4bd72cd469c2 100644 --- a/data/reusables/audit_log/audit-log-search.md +++ b/data/reusables/audit_log/audit-log-search.md @@ -1,6 +1,6 @@ {% data reusables.audit_log.audit-log-search-list-info-about-action %} -Note that you cannot search for entries using text. You can, however, construct search queries using a variety of filters. Many operators used when querying the log, such as `-`, `>`, or `<`, match the same format as searching across {% data variables.product.product_name %}. For more information, see [AUTOTITLE](/search-github/getting-started-with-searching-on-github/about-searching-on-github). +Note that you cannot search for entries using text. You can, however, construct search queries using a variety of filters. Many operators used when querying the log, such as `-`, `>`, or `<`, match the same format as searching across {% data variables.product.github %}. For more information, see [AUTOTITLE](/search-github/getting-started-with-searching-on-github/about-searching-on-github). {% data reusables.audit_log.audit-log-search-by-operation %} diff --git a/data/reusables/audit_log/retention-periods.md b/data/reusables/audit_log/retention-periods.md index e553639ff8bd..3c3d53c69f75 100644 --- a/data/reusables/audit_log/retention-periods.md +++ b/data/reusables/audit_log/retention-periods.md @@ -1,3 +1,3 @@ -The audit log lists events triggered by activities that affect your enterprise{% ifversion ghes %}. Audit logs for {% data variables.product.product_name %} are retained indefinitely, unless an enterprise owner configured a different retention period. See [AUTOTITLE](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/configuring-the-audit-log-for-your-enterprise).{% else %} within the last 180 days. {% data reusables.audit_log.git-events-retention-period %}{% endif %} +The audit log lists events triggered by activities that affect your enterprise{% ifversion ghes %}. Audit logs for {% data variables.product.github %} are retained indefinitely, unless an enterprise owner configured a different retention period. See [AUTOTITLE](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/configuring-the-audit-log-for-your-enterprise).{% else %} within the last 180 days. {% data reusables.audit_log.git-events-retention-period %}{% endif %} {% data reusables.audit_log.only-three-months-displayed %} diff --git a/data/reusables/billing/about-billing.md b/data/reusables/billing/about-billing.md index f8871c21f7b1..5dc83db90c7b 100644 --- a/data/reusables/billing/about-billing.md +++ b/data/reusables/billing/about-billing.md @@ -1 +1 @@ -The bill for each account on {% data variables.product.product_name %} consists of the account's plan, plus other any other subscriptions and usage-based billing for the account. +The bill for each account on {% data variables.product.github %} consists of the account's plan, plus other any other subscriptions and usage-based billing for the account. diff --git a/data/reusables/branches/new-repo-default-branch.md b/data/reusables/branches/new-repo-default-branch.md index 8c00d774f10d..fbc3c8c26d4b 100644 --- a/data/reusables/branches/new-repo-default-branch.md +++ b/data/reusables/branches/new-repo-default-branch.md @@ -1 +1 @@ -When you create a repository with content on {% data variables.product.prodname_dotcom %}, {% data variables.product.product_name %} creates the repository with a single branch. This first branch in the repository is the default branch. +When you create a repository with content on {% data variables.product.github %}, {% data variables.product.github %} creates the repository with a single branch. This first branch in the repository is the default branch. diff --git a/data/reusables/classroom/classroom-creates-group-repositories.md b/data/reusables/classroom/classroom-creates-group-repositories.md index 10cdc5924a51..7803e55ed6ff 100644 --- a/data/reusables/classroom/classroom-creates-group-repositories.md +++ b/data/reusables/classroom/classroom-creates-group-repositories.md @@ -1 +1 @@ -For each group assignment, {% data variables.product.prodname_classroom %} automatically creates a single shared repository for the team to access. The repository can be empty, or you can create the repository from a template repository with starter code, documentation, tests, and other resources. The repository belongs to your organization account on {% data variables.product.product_name %}, and {% data variables.product.prodname_classroom %} grants access to teams that students create or join when accepting the assignment. +For each group assignment, {% data variables.product.prodname_classroom %} automatically creates a single shared repository for the team to access. The repository can be empty, or you can create the repository from a template repository with starter code, documentation, tests, and other resources. The repository belongs to your organization account on {% data variables.product.github %}, and {% data variables.product.prodname_classroom %} grants access to teams that students create or join when accepting the assignment. diff --git a/data/reusables/classroom/classroom-creates-individual-repositories.md b/data/reusables/classroom/classroom-creates-individual-repositories.md index 4108abf9ad14..725b55d6be01 100644 --- a/data/reusables/classroom/classroom-creates-individual-repositories.md +++ b/data/reusables/classroom/classroom-creates-individual-repositories.md @@ -1 +1 @@ -When a student accepts an assignment, {% data variables.product.prodname_classroom %} automatically creates a new repository for the student. The repositories can be empty, or you can create the repositories from a template repository with starter code, documentation, tests, and other resources. Each assignment repository belongs to your organization account on {% data variables.product.product_name %}. +When a student accepts an assignment, {% data variables.product.prodname_classroom %} automatically creates a new repository for the student. The repositories can be empty, or you can create the repositories from a template repository with starter code, documentation, tests, and other resources. Each assignment repository belongs to your organization account on {% data variables.product.github %}. diff --git a/data/reusables/classroom/invitation-url-warning.md b/data/reusables/classroom/invitation-url-warning.md index 0e667651eff2..791354ff9a8c 100644 --- a/data/reusables/classroom/invitation-url-warning.md +++ b/data/reusables/classroom/invitation-url-warning.md @@ -1,2 +1,2 @@ > [!WARNING] -> Be careful where you share invitation URLs. Anyone with an invitation URL for an assignment can accept the invitation and associate a personal account on {% data variables.product.product_name %} with an identifier in your roster. +> Be careful where you share invitation URLs. Anyone with an invitation URL for an assignment can accept the invitation and associate a personal account on {% data variables.product.github %} with an identifier in your roster. diff --git a/data/reusables/classroom/you-can-choose-a-template-repository.md b/data/reusables/classroom/you-can-choose-a-template-repository.md index 3f74c6914e6e..f26de704976a 100644 --- a/data/reusables/classroom/you-can-choose-a-template-repository.md +++ b/data/reusables/classroom/you-can-choose-a-template-repository.md @@ -1,4 +1,4 @@ You can optionally choose a template repository as starter code for the assignment. For more information, see [AUTOTITLE](/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-assignment-from-a-template-repository). > [!NOTE] -> The template repository must belong to your organization or be a public repository on {% data variables.product.product_name %}. +> The template repository must belong to your organization or be a public repository on {% data variables.product.github %}. diff --git a/data/reusables/cli/cli-intro.md b/data/reusables/cli/cli-intro.md index b291509f05e0..89fcc2853d95 100644 --- a/data/reusables/cli/cli-intro.md +++ b/data/reusables/cli/cli-intro.md @@ -1 +1 @@ -{% data variables.product.prodname_cli %} is a command-line tool that brings pull requests, issues, {% data variables.product.prodname_actions %}, and other {% data variables.product.product_name %} features to your terminal, so you can do all your work in one place. +{% data variables.product.prodname_cli %} is a command-line tool that brings pull requests, issues, {% data variables.product.prodname_actions %}, and other {% data variables.product.github %} features to your terminal, so you can do all your work in one place. diff --git a/data/reusables/codespaces/machine-types-for-unpublished-codespaces.md b/data/reusables/codespaces/machine-types-for-unpublished-codespaces.md index c9aafc509a7b..8bc4c121ec92 100644 --- a/data/reusables/codespaces/machine-types-for-unpublished-codespaces.md +++ b/data/reusables/codespaces/machine-types-for-unpublished-codespaces.md @@ -1 +1 @@ -Unpublished codespaces (codespaces created from a template that are not linked to a repository on {% data variables.product.product_name %}) always run on a virtual machine with the same specifications. You can't change the machine type of an unpublished codespace. +Unpublished codespaces (codespaces created from a template that are not linked to a repository on {% data variables.product.github %}) always run on a virtual machine with the same specifications. You can't change the machine type of an unpublished codespace. diff --git a/data/reusables/codespaces/starting-new-project-template.md b/data/reusables/codespaces/starting-new-project-template.md index a0ac56ec06d3..4db71cfa45c8 100644 --- a/data/reusables/codespaces/starting-new-project-template.md +++ b/data/reusables/codespaces/starting-new-project-template.md @@ -1 +1 @@ -If you're starting a new project, you might want to create a codespace from a template and publish to a repository on {% data variables.product.product_name %} later. +If you're starting a new project, you might want to create a codespace from a template and publish to a repository on {% data variables.product.github %} later. diff --git a/data/reusables/command_line/manipulating_file_prereqs.md b/data/reusables/command_line/manipulating_file_prereqs.md index 5451f1ea9054..c7f315555778 100644 --- a/data/reusables/command_line/manipulating_file_prereqs.md +++ b/data/reusables/command_line/manipulating_file_prereqs.md @@ -1,4 +1,4 @@ This procedure assumes you've already: -* [Created a repository on {% data variables.product.product_name %}](/repositories/creating-and-managing-repositories/creating-a-new-repository), or have an existing repository owned by someone else you'd like to contribute to +* [Created a repository on {% data variables.product.github %}](/repositories/creating-and-managing-repositories/creating-a-new-repository), or have an existing repository owned by someone else you'd like to contribute to * [Cloned the repository locally on your computer](/repositories/creating-and-managing-repositories/cloning-a-repository) diff --git a/data/reusables/dashboard/access-org-dashboard.md b/data/reusables/dashboard/access-org-dashboard.md index 91ea900c4e63..41f4d0ba2d03 100644 --- a/data/reusables/dashboard/access-org-dashboard.md +++ b/data/reusables/dashboard/access-org-dashboard.md @@ -1,4 +1,4 @@ -1. To access the dashboard page, in the upper-left corner of any page on {% data variables.product.product_name %}, click the {% octicon "mark-github" aria-label="The github octocat logo" %}. +1. To access the dashboard page, in the upper-left corner of any page on {% data variables.product.github %}, click the {% octicon "mark-github" aria-label="The github octocat logo" %}. 1. To switch to your organization dashboard, in the upper-left corner of the page, select your username, then from the dropdown menu, click the desired organization. ![Screenshot of the "Switch dashboard context" menu for a personal account. The menu lists organizations linked to the personal account.](/assets/images/help/dashboard/dashboard-context-switcher.png)