diff --git a/data/reusables/dependency-graph/sbom-export.md b/data/reusables/dependency-graph/sbom-export.md index 7abc0d824c80..5b7ed57c9e6c 100644 --- a/data/reusables/dependency-graph/sbom-export.md +++ b/data/reusables/dependency-graph/sbom-export.md @@ -1 +1 @@ -If you have at least read access to the repository, you can export the dependency graph for the repository as an SPDX-compatible, Software Bill of Materials (SBOM), via the {% data variables.product.prodname_dotcom %} UI or {% data variables.product.company_short %} REST API. For more information, see "[AUTOTITLE](/code-security/supply-chain-security/understanding-your-software-supply-chain/exporting-a-software-bill-of-materials-for-your-repository)." +If you have at least read access to the repository, you can export the dependency graph for the repository as an SPDX-compatible, Software Bill of Materials (SBOM), via the {% data variables.product.prodname_dotcom %} UI or {% data variables.product.company_short %} REST API. For more information, see [AUTOTITLE](/code-security/supply-chain-security/understanding-your-software-supply-chain/exporting-a-software-bill-of-materials-for-your-repository). diff --git a/data/reusables/dependency-graph/supported-package-ecosystems.md b/data/reusables/dependency-graph/supported-package-ecosystems.md index 41d7d3a34bb1..980defbf2e1b 100644 --- a/data/reusables/dependency-graph/supported-package-ecosystems.md +++ b/data/reusables/dependency-graph/supported-package-ecosystems.md @@ -19,5 +19,5 @@ > [!NOTE] > * If you list your Python dependencies within a `setup.py` file, we may not be able to parse and list every dependency in your project. -> * {% data variables.product.prodname_actions %} workflows must be located in the `.github/workflows/` directory of a repository to be recognized as manifests. Any actions or workflows referenced using the syntax `jobs[*].steps[*].uses` or `jobs..uses` will be parsed as dependencies. For more information, see "[AUTOTITLE](/actions/using-workflows/workflow-syntax-for-github-actions)." -> * {% data reusables.dependabot.dependabot-alert-actions-semver %} For more information, see "[AUTOTITLE](/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)" and "[AUTOTITLE](/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates)." +> * {% data variables.product.prodname_actions %} workflows must be located in the `.github/workflows/` directory of a repository to be recognized as manifests. Any actions or workflows referenced using the syntax `jobs[*].steps[*].uses` or `jobs..uses` will be parsed as dependencies. For more information, see [AUTOTITLE](/actions/using-workflows/workflow-syntax-for-github-actions). +> * {% data reusables.dependabot.dependabot-alert-actions-semver %} For more information, see [AUTOTITLE](/code-security/dependabot/dependabot-alerts/about-dependabot-alerts) and [AUTOTITLE](/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates). diff --git a/data/reusables/dependency-review/about-dependency-review-action2.md b/data/reusables/dependency-review/about-dependency-review-action2.md index 09a9ec45eab5..18d58ccf0025 100644 --- a/data/reusables/dependency-review/about-dependency-review-action2.md +++ b/data/reusables/dependency-review/about-dependency-review-action2.md @@ -1 +1 @@ -By default, the {% data variables.dependency-review.action_name %} check will fail if it discovers any vulnerable packages. A failed check blocks a pull request from being merged when the repository owner requires the dependency review check to pass. For more information, see "[AUTOTITLE](/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/about-protected-branches#require-status-checks-before-merging)." +By default, the {% data variables.dependency-review.action_name %} check will fail if it discovers any vulnerable packages. A failed check blocks a pull request from being merged when the repository owner requires the dependency review check to pass. For more information, see [AUTOTITLE](/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/about-protected-branches#require-status-checks-before-merging). diff --git a/data/reusables/dependency-review/dependency-review-action-overview.md b/data/reusables/dependency-review/dependency-review-action-overview.md index b572ec18e7a9..ebd90afa27c1 100644 --- a/data/reusables/dependency-review/dependency-review-action-overview.md +++ b/data/reusables/dependency-review/dependency-review-action-overview.md @@ -1,3 +1,3 @@ The {% data variables.dependency-review.action_name %} scans your pull requests for dependency changes and raises an error if any new dependencies have known vulnerabilities. The action is supported by an API endpoint that compares the dependencies between two revisions and reports any differences. -For more information about the action and the API endpoint, see the [`dependency-review-action`](https://github.com/actions/dependency-review-action) documentation, and "[AUTOTITLE](/rest/dependency-graph/dependency-review)." +For more information about the action and the API endpoint, see the [`dependency-review-action`](https://github.com/actions/dependency-review-action) documentation, and [AUTOTITLE](/rest/dependency-graph/dependency-review). diff --git a/data/reusables/dependency-review/dependency-review-enabled-ghes.md b/data/reusables/dependency-review/dependency-review-enabled-ghes.md index ccf3911d955c..4dd98ffcf66d 100644 --- a/data/reusables/dependency-review/dependency-review-enabled-ghes.md +++ b/data/reusables/dependency-review/dependency-review-enabled-ghes.md @@ -1,3 +1,3 @@ {% ifversion ghes %} -After you enable the dependency graph, users will have access to the dependency review feature. {% data reusables.dependency-review.short-summary %} For more information, see "[AUTOTITLE](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review)." +After you enable the dependency graph, users will have access to the dependency review feature. {% data reusables.dependency-review.short-summary %} For more information, see [AUTOTITLE](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review). {% endif %} diff --git a/data/reusables/dependency-review/org-level-enforcement.md b/data/reusables/dependency-review/org-level-enforcement.md index 724247407a63..b7a8d2b90b1b 100644 --- a/data/reusables/dependency-review/org-level-enforcement.md +++ b/data/reusables/dependency-review/org-level-enforcement.md @@ -1,5 +1,5 @@ {% ifversion repo-rules %} -Organization owners can roll out dependency review at scale by enforcing the use of the {% data variables.dependency-review.action_name %} across repositories in the organization. This involves the use of repository rulesets for which you'll set the {% data variables.dependency-review.action_name %} as a required workflow, which means that pull requests can only be merged once the workflow passes all the required checks. For more information, see "[AUTOTITLE](/code-security/supply-chain-security/understanding-your-software-supply-chain/enforcing-dependency-review-across-an-organization)." +Organization owners can roll out dependency review at scale by enforcing the use of the {% data variables.dependency-review.action_name %} across repositories in the organization. This involves the use of repository rulesets for which you'll set the {% data variables.dependency-review.action_name %} as a required workflow, which means that pull requests can only be merged once the workflow passes all the required checks. For more information, see [AUTOTITLE](/code-security/supply-chain-security/understanding-your-software-supply-chain/enforcing-dependency-review-across-an-organization). {% endif %} diff --git a/data/reusables/dependency-submission/about-dependency-submission.md b/data/reusables/dependency-submission/about-dependency-submission.md index 5cd9fb70da9f..751da226dac0 100644 --- a/data/reusables/dependency-submission/about-dependency-submission.md +++ b/data/reusables/dependency-submission/about-dependency-submission.md @@ -1,8 +1,8 @@ You can use the REST API to submit dependencies for a project. This enables you to add dependencies, such as those resolved when software is compiled or built, to {% data variables.product.prodname_dotcom %}'s dependency graph feature, providing a more complete picture of all of your project's dependencies. -The dependency graph shows any dependencies you submit using the API in addition to any dependencies that are identified from manifest or lock files in the repository (for example, a `package-lock.json` file in a JavaScript project). For more information about viewing the dependency graph, see "[AUTOTITLE](/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository#viewing-the-dependency-graph)." +The dependency graph shows any dependencies you submit using the API in addition to any dependencies that are identified from manifest or lock files in the repository (for example, a `package-lock.json` file in a JavaScript project). For more information about viewing the dependency graph, see [AUTOTITLE](/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository#viewing-the-dependency-graph). -Submitted dependencies will receive {% data variables.product.prodname_dependabot_alerts %} and {% data variables.product.prodname_dependabot_security_updates %} for any known vulnerabilities. You will only get {% data variables.product.prodname_dependabot_alerts %} for dependencies that are from one of the supported ecosystems for the {% data variables.product.prodname_advisory_database %}. For more information about these ecosystems, see "[AUTOTITLE](/code-security/security-advisories/global-security-advisories/about-the-github-advisory-database#github-reviewed-advisories)." For transitive dependencies submitted via the {% data variables.dependency-submission-api.name %}, {% data variables.product.prodname_dependabot %} will automatically open pull requests to update the parent dependency, if an update is available. +Submitted dependencies will receive {% data variables.product.prodname_dependabot_alerts %} and {% data variables.product.prodname_dependabot_security_updates %} for any known vulnerabilities. You will only get {% data variables.product.prodname_dependabot_alerts %} for dependencies that are from one of the supported ecosystems for the {% data variables.product.prodname_advisory_database %}. For more information about these ecosystems, see [AUTOTITLE](/code-security/security-advisories/global-security-advisories/about-the-github-advisory-database#github-reviewed-advisories). For transitive dependencies submitted via the {% data variables.dependency-submission-api.name %}, {% data variables.product.prodname_dependabot %} will automatically open pull requests to update the parent dependency, if an update is available. {% ifversion dependency-review-submission-api %}Submitted dependencies will be shown in dependency review, but are _not_ available in your organization's dependency insights. diff --git a/data/reusables/dependency-submission/dependency-submission-link.md b/data/reusables/dependency-submission/dependency-submission-link.md index 82431bf45ddf..32cee1443fb2 100644 --- a/data/reusables/dependency-submission/dependency-submission-link.md +++ b/data/reusables/dependency-submission/dependency-submission-link.md @@ -1,2 +1,2 @@ Additionally, you can use the {% data variables.dependency-submission-api.name %} to submit dependencies from the package manager or ecosystem of your choice, even if the ecosystem is not supported by dependency graph for manifest or lock file analysis. -{% ifversion dependency-graph-repository-view-update %}Dependencies submitted to a project using the {% data variables.dependency-submission-api.name %} will show which detector was used for their submission and when they were submitted.{% elsif ghes %} The dependency graph will display the submitted dependencies grouped by ecosystem, but separately from the dependencies parsed from manifest or lock files.{% else %}{% endif %} For more information on the {% data variables.dependency-submission-api.name %}, see "[AUTOTITLE](/code-security/supply-chain-security/understanding-your-software-supply-chain/using-the-dependency-submission-api)." +{% ifversion dependency-graph-repository-view-update %}Dependencies submitted to a project using the {% data variables.dependency-submission-api.name %} will show which detector was used for their submission and when they were submitted.{% elsif ghes %} The dependency graph will display the submitted dependencies grouped by ecosystem, but separately from the dependencies parsed from manifest or lock files.{% else %}{% endif %} For more information on the {% data variables.dependency-submission-api.name %}, see [AUTOTITLE](/code-security/supply-chain-security/understanding-your-software-supply-chain/using-the-dependency-submission-api). diff --git a/data/reusables/desktop/about-github-desktop.md b/data/reusables/desktop/about-github-desktop.md index 48a449790a1d..98164ec6107f 100644 --- a/data/reusables/desktop/about-github-desktop.md +++ b/data/reusables/desktop/about-github-desktop.md @@ -1 +1 @@ -{% data variables.product.prodname_desktop %} is a free, open source application that helps you to work with code hosted on {% data variables.product.prodname_dotcom %} or other Git hosting services. With {% data variables.product.prodname_desktop %}, you can perform Git commands, such as committing and pushing changes, in a graphical user interface, rather than using the command line. For more information, see "[AUTOTITLE](/desktop/installing-and-configuring-github-desktop/overview/about-github-desktop)." +{% data variables.product.prodname_desktop %} is a free, open source application that helps you to work with code hosted on {% data variables.product.prodname_dotcom %} or other Git hosting services. With {% data variables.product.prodname_desktop %}, you can perform Git commands, such as committing and pushing changes, in a graphical user interface, rather than using the command line. For more information, see [AUTOTITLE](/desktop/installing-and-configuring-github-desktop/overview/about-github-desktop). diff --git a/data/reusables/desktop/checked-out-pr.md b/data/reusables/desktop/checked-out-pr.md index 665cffecb01a..eff1970c2d07 100644 --- a/data/reusables/desktop/checked-out-pr.md +++ b/data/reusables/desktop/checked-out-pr.md @@ -1 +1 @@ -When you have opened a pull request branch, you can view the contents of the branch in an editor, view the diff and commit history of the contributor's updates, and view and re-run checks. For more information, see "[Working with a pull request in {% data variables.product.prodname_desktop %}](#working-with-a-pull-request-in-github-desktop)." +When you have opened a pull request branch, you can view the contents of the branch in an editor, view the diff and commit history of the contributor's updates, and view and re-run checks. For more information, see [Working with a pull request in {% data variables.product.prodname_desktop %}](#working-with-a-pull-request-in-github-desktop). diff --git a/data/reusables/desktop/get-an-account.md b/data/reusables/desktop/get-an-account.md index ca9b9d6daecb..50d3340168a5 100644 --- a/data/reusables/desktop/get-an-account.md +++ b/data/reusables/desktop/get-an-account.md @@ -1 +1 @@ -you must already have an account on {% data variables.product.github %}.{% ifversion fpt or ghec %} For more information, see "[AUTOTITLE](/get-started/start-your-journey/creating-an-account-on-github)."{% endif %}{% ifversion ghec %} If you're part of an organization that uses {% data variables.product.prodname_emus %} and you do not have an account, contact your enterprise administrator.{% elsif ghes %} If you're a member of an organization that uses {% data variables.product.product_name %} and you do not have an account, contact your {% data variables.product.prodname_enterprise %} site administrator.{% endif %} +you must already have an account on {% data variables.product.github %}.{% ifversion fpt or ghec %} For more information, see [AUTOTITLE](/get-started/start-your-journey/creating-an-account-on-github).{% endif %}{% ifversion ghec %} If you're part of an organization that uses {% data variables.product.prodname_emus %} and you do not have an account, contact your enterprise administrator.{% elsif ghes %} If you're a member of an organization that uses {% data variables.product.product_name %} and you do not have an account, contact your {% data variables.product.prodname_enterprise %} site administrator.{% endif %} diff --git a/data/reusables/desktop/protected-branches.md b/data/reusables/desktop/protected-branches.md index c2b43ebc675d..d1412be22443 100644 --- a/data/reusables/desktop/protected-branches.md +++ b/data/reusables/desktop/protected-branches.md @@ -1 +1 @@ -Repository administrators 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 enable other protected branch settings to enforce specific workflows before a branch can be merged. For more information, see "[AUTOTITLE](/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/about-protected-branches)." +Repository administrators 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 enable other protected branch settings to enforce specific workflows before a branch can be merged. For more information, see [AUTOTITLE](/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/about-protected-branches). diff --git a/data/reusables/desktop/resolve-merge-conflicts.md b/data/reusables/desktop/resolve-merge-conflicts.md index ae63e2ac8030..aaf5d98775e5 100644 --- a/data/reusables/desktop/resolve-merge-conflicts.md +++ b/data/reusables/desktop/resolve-merge-conflicts.md @@ -1 +1 @@ -1. Resolve any merge conflicts in your preferred way, using a text editor, the command line, or another tool. For more information, see "[AUTOTITLE](/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts)." +1. Resolve any merge conflicts in your preferred way, using a text editor, the command line, or another tool. For more information, see [AUTOTITLE](/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts). diff --git a/data/reusables/developer-site/limit_workflow_to_activity_types.md b/data/reusables/developer-site/limit_workflow_to_activity_types.md index 61c2dff791ce..58f7e10690df 100644 --- a/data/reusables/developer-site/limit_workflow_to_activity_types.md +++ b/data/reusables/developer-site/limit_workflow_to_activity_types.md @@ -1 +1 @@ -By default, all activity types trigger workflows that run on this event. You can limit your workflow runs to specific activity types using the `types` keyword. For more information, see "[AUTOTITLE](/actions/using-workflows/workflow-syntax-for-github-actions#onevent_nametypes)." +By default, all activity types trigger workflows that run on this event. You can limit your workflow runs to specific activity types using the `types` keyword. For more information, see [AUTOTITLE](/actions/using-workflows/workflow-syntax-for-github-actions#onevent_nametypes). diff --git a/data/reusables/developer-site/pull_request_forked_repos_link.md b/data/reusables/developer-site/pull_request_forked_repos_link.md index aab0a7b2bd7a..66dc205abb6b 100644 --- a/data/reusables/developer-site/pull_request_forked_repos_link.md +++ b/data/reusables/developer-site/pull_request_forked_repos_link.md @@ -2,17 +2,17 @@ Workflows don't run in forked repositories by default. You must enable GitHub Actions in the **Actions** tab of the forked repository. -{% data reusables.actions.forked-secrets %} The `GITHUB_TOKEN` has read-only permissions in pull requests from forked repositories. For more information, see "[AUTOTITLE](/actions/security-guides/automatic-token-authentication)." +{% data reusables.actions.forked-secrets %} The `GITHUB_TOKEN` has read-only permissions in pull requests from forked repositories. For more information, see [AUTOTITLE](/actions/security-guides/automatic-token-authentication). #### Pull request events for forked repositories For pull requests from a forked repository to the base repository, {% data variables.product.product_name %} sends the `pull_request`, `issue_comment`, `pull_request_review_comment`, `pull_request_review`, and `pull_request_target` events to the base repository. No pull request events occur on the forked repository. {% ifversion fpt or ghec %} -When a first-time contributor submits a pull request to a public repository, a maintainer with write access may need to approve running workflows on the pull request. For more information, see "[AUTOTITLE](/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks)." +When a first-time contributor submits a pull request to a public repository, a maintainer with write access may need to approve running workflows on the pull request. For more information, see [AUTOTITLE](/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks). {% endif %} -For pull requests from a forked repository to a private repository, workflows only run when they are enabled, see "[AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#enabling-workflows-for-forks-of-private-repositories)." +For pull requests from a forked repository to a private repository, workflows only run when they are enabled, see [AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#enabling-workflows-for-forks-of-private-repositories). > [!NOTE] > Workflows triggered by {% data variables.product.prodname_dependabot %} pull requests are treated as though they are from a forked repository, and are also subject to these restrictions. diff --git a/data/reusables/discussions/add-category-to-section.md b/data/reusables/discussions/add-category-to-section.md index fbe8d3e8fc28..9bd25004b382 100644 --- a/data/reusables/discussions/add-category-to-section.md +++ b/data/reusables/discussions/add-category-to-section.md @@ -1,3 +1,3 @@ -1. Optionally, add the category to a section. A category can only belong to one section at a time. For information on how to create a section, see "[Creating a section](#creating-a-section)." +1. Optionally, add the category to a section. A category can only belong to one section at a time. For information on how to create a section, see [Creating a section](#creating-a-section). ![Screenshot of part of the "Create category" page, showing the option to add a category to a section.](/assets/images/help/discussions/add-category-to-section.png) diff --git a/data/reusables/discussions/marking-a-comment-as-an-answer.md b/data/reusables/discussions/marking-a-comment-as-an-answer.md index 45c922b5b3b7..cabc9db14349 100644 --- a/data/reusables/discussions/marking-a-comment-as-an-answer.md +++ b/data/reusables/discussions/marking-a-comment-as-an-answer.md @@ -1,4 +1,4 @@ -You can mark a comment in the discussion as an answer to the discussion if a discussion is within a category that accepts answers. For more information, see "[AUTOTITLE](/discussions/collaborating-with-your-community-using-discussions/about-discussions#about-categories-and-formats-for-discussions)." +You can mark a comment in the discussion as an answer to the discussion if a discussion is within a category that accepts answers. For more information, see [AUTOTITLE](/discussions/collaborating-with-your-community-using-discussions/about-discussions#about-categories-and-formats-for-discussions). When you mark a question as an answer, {% data variables.product.product_name %} will highlight the comment and replies to the comment to help visitors quickly find the answer. diff --git a/data/reusables/discussions/you-can-label-discussions.md b/data/reusables/discussions/you-can-label-discussions.md index 763ff2665324..a5d58911c758 100644 --- a/data/reusables/discussions/you-can-label-discussions.md +++ b/data/reusables/discussions/you-can-label-discussions.md @@ -1 +1 @@ -To organize discussions more granularly, you can apply labels. For example, you can use labels to indicate the status of a discussion to make triaging more efficient. Each repository has one shared set of labels for issues, pull requests, and discussions. For more information, see "[AUTOTITLE](/issues/using-labels-and-milestones-to-track-work/managing-labels)." +To organize discussions more granularly, you can apply labels. For example, you can use labels to indicate the status of a discussion to make triaging more efficient. Each repository has one shared set of labels for issues, pull requests, and discussions. For more information, see [AUTOTITLE](/issues/using-labels-and-milestones-to-track-work/managing-labels). diff --git a/data/reusables/discussions/you-can-use-discussions.md b/data/reusables/discussions/you-can-use-discussions.md index 0196fa50085a..d615f596c7ff 100644 --- a/data/reusables/discussions/you-can-use-discussions.md +++ b/data/reusables/discussions/you-can-use-discussions.md @@ -1 +1 @@ -You can use {% data variables.product.prodname_discussions %} to ask and answer questions, share information, make announcements, and conduct or participate in conversations about a project. For more information, see "[AUTOTITLE](/discussions/collaborating-with-your-community-using-discussions/about-discussions)." +You can use {% data variables.product.prodname_discussions %} to ask and answer questions, share information, make announcements, and conduct or participate in conversations about a project. For more information, see [AUTOTITLE](/discussions/collaborating-with-your-community-using-discussions/about-discussions). diff --git a/data/reusables/docs/ghec-docs.md b/data/reusables/docs/ghec-docs.md index e7612d06668f..75dccd0c8eea 100644 --- a/data/reusables/docs/ghec-docs.md +++ b/data/reusables/docs/ghec-docs.md @@ -1 +1 @@ -You can read documentation that reflects the features available with {% data variables.product.prodname_ghe_cloud %}. For more information, see "[AUTOTITLE](/get-started/learning-about-github/about-versions-of-github-docs)." +You can read documentation that reflects the features available with {% data variables.product.prodname_ghe_cloud %}. For more information, see [AUTOTITLE](/get-started/learning-about-github/about-versions-of-github-docs). diff --git a/data/reusables/docs/you-can-read-docs-for-your-product.md b/data/reusables/docs/you-can-read-docs-for-your-product.md index 491aabb29c72..879bc2c0ed85 100644 --- a/data/reusables/docs/you-can-read-docs-for-your-product.md +++ b/data/reusables/docs/you-can-read-docs-for-your-product.md @@ -1 +1 @@ -You can read documentation that reflects the features available to you on {% data variables.product.product_name %}. For more information, see "[AUTOTITLE](/get-started/learning-about-github/about-versions-of-github-docs)." +You can read documentation that reflects the features available to you on {% data variables.product.product_name %}. For more information, see [AUTOTITLE](/get-started/learning-about-github/about-versions-of-github-docs). diff --git a/data/reusables/dotcom_billing/payment-methods.md b/data/reusables/dotcom_billing/payment-methods.md index 792afc555669..1c29db6c741b 100644 --- a/data/reusables/dotcom_billing/payment-methods.md +++ b/data/reusables/dotcom_billing/payment-methods.md @@ -2,7 +2,7 @@ If your {% data variables.product.prodname_ghe_cloud %} account uses metered billing, you can pay for your licenses with a credit card, PayPal, or through an Azure subscription. For purchase orders, contact your account manager in {% data variables.contact.contact_enterprise_sales %}. -> [!IMPORTANT] If you currently pay for your {% data variables.product.prodname_enterprise %} licenses through a volume, subscription, or prepaid agreement, you will continue to be billed in this way until your agreement expires. At renewal, you have the option to switch to the metered billing model. See, "[AUTOTITLE](/billing/using-the-enhanced-billing-platform-for-enterprises/getting-started-with-the-enhanced-billing-platform)." +> [!IMPORTANT] If you currently pay for your {% data variables.product.prodname_enterprise %} licenses through a volume, subscription, or prepaid agreement, you will continue to be billed in this way until your agreement expires. At renewal, you have the option to switch to the metered billing model. See, [AUTOTITLE](/billing/using-the-enhanced-billing-platform-for-enterprises/getting-started-with-the-enhanced-billing-platform). > > If you do not have an account manager and pay for {% data variables.product.prodname_enterprise %} via credit card or PayPal, the transition to usage-based billing will be prompted by the product in the future, but this is not currently supported. diff --git a/data/reusables/dotcom_billing/view-all-subscriptions.md b/data/reusables/dotcom_billing/view-all-subscriptions.md index 5c427d90d515..9007c77c48e1 100644 --- a/data/reusables/dotcom_billing/view-all-subscriptions.md +++ b/data/reusables/dotcom_billing/view-all-subscriptions.md @@ -1 +1 @@ -To view all the subscriptions for your account on {% data variables.product.prodname_dotcom %}, see "[AUTOTITLE](/billing/managing-your-github-billing-settings/viewing-your-subscriptions-and-billing-date)." +To view all the subscriptions for your account on {% data variables.product.prodname_dotcom %}, see [AUTOTITLE](/billing/managing-your-github-billing-settings/viewing-your-subscriptions-and-billing-date). diff --git a/data/reusables/education/about-github-education-link.md b/data/reusables/education/about-github-education-link.md index 853c682acab7..0a61494967cd 100644 --- a/data/reusables/education/about-github-education-link.md +++ b/data/reusables/education/about-github-education-link.md @@ -1,3 +1,3 @@ As a student or faculty member at an accredited educational institution, you can apply for {% data variables.product.prodname_global_campus %}. {% data variables.product.prodname_global_campus %} is a portal that allows the GitHub Education Community to access their education benefits—all in one place! The {% data variables.product.prodname_global_campus %} portal includes access to {% data variables.product.prodname_education_community_with_url %}, industry tools used by professional developers, events, [Campus TV](https://www.twitch.tv/githubeducation) content, {% data variables.product.prodname_classroom_with_url %}, [{% data variables.product.prodname_community_exchange %}](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/about-github-community-exchange), {% data variables.product.prodname_student_pack %}, and other exclusive features to help students and teachers shape the next generation of software development. -Before applying for an individual discount, check if your learning community is already partnered with us as a {% data variables.product.prodname_campus_program %} school. For more information, see "[AUTOTITLE](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution/about-github-campus-program)." +Before applying for an individual discount, check if your learning community is already partnered with us as a {% data variables.product.prodname_campus_program %} school. For more information, see [AUTOTITLE](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution/about-github-campus-program). diff --git a/data/reusables/education/access-github-community-exchange.md b/data/reusables/education/access-github-community-exchange.md index 476212bac439..7cc77cac200a 100644 --- a/data/reusables/education/access-github-community-exchange.md +++ b/data/reusables/education/access-github-community-exchange.md @@ -2,6 +2,6 @@ To access {% data variables.product.prodname_community_exchange %}, visit your { If you're a student or faculty member at an accredited educational institution, you can apply for {% data variables.product.prodname_education %} benefits, which includes access to {% data variables.product.prodname_community_exchange %} within {% data variables.product.prodname_global_campus %}. -* If you’re a student and you haven't joined {% data variables.product.prodname_education %} yet, apply using the [student application form]( https://education.github.com/discount_requests/student_application). For more information, see "[AUTOTITLE](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/about-github-global-campus-for-students)." +* If you’re a student and you haven't joined {% data variables.product.prodname_education %} yet, apply using the [student application form]( https://education.github.com/discount_requests/student_application). For more information, see [AUTOTITLE](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/about-github-global-campus-for-students). -* If you’re an educator and you haven't joined {% data variables.product.prodname_education %} yet, apply using the [teacher application form]( https://education.github.com/discount_requests/teacher_application). For more information, see "[AUTOTITLE](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/apply-to-github-global-campus-as-a-teacher)." +* If you’re an educator and you haven't joined {% data variables.product.prodname_education %} yet, apply using the [teacher application form]( https://education.github.com/discount_requests/teacher_application). For more information, see [AUTOTITLE](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/apply-to-github-global-campus-as-a-teacher). diff --git a/data/reusables/education/apply-for-team.md b/data/reusables/education/apply-for-team.md index 14722641748f..c9c29a9c8be0 100644 --- a/data/reusables/education/apply-for-team.md +++ b/data/reusables/education/apply-for-team.md @@ -1 +1 @@ -* Apply for free [{% data variables.product.prodname_team %}](/get-started/learning-about-github/githubs-plans), which allows unlimited users and private repositories. For more information, see "[AUTOTITLE](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-education-for-teachers/apply-to-github-education-as-a-teacher)." +* Apply for free [{% data variables.product.prodname_team %}](/get-started/learning-about-github/githubs-plans), which allows unlimited users and private repositories. For more information, see [AUTOTITLE](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-education-for-teachers/apply-to-github-education-as-a-teacher). diff --git a/data/reusables/education/student-codespaces-benefit.md b/data/reusables/education/student-codespaces-benefit.md index 6da39f0277a3..57015ec66351 100644 --- a/data/reusables/education/student-codespaces-benefit.md +++ b/data/reusables/education/student-codespaces-benefit.md @@ -1 +1 @@ -Verified students get free use of {% data variables.product.prodname_github_codespaces %}, up to 180 core hours per month, for their personal accounts. The monthly amount of storage and core hours of usage available to students is equivalent to the amount included with {% data variables.product.prodname_pro %} accounts. For more information, see "[AUTOTITLE](/billing/managing-billing-for-your-products/managing-billing-for-github-codespaces/about-billing-for-github-codespaces)." +Verified students get free use of {% data variables.product.prodname_github_codespaces %}, up to 180 core hours per month, for their personal accounts. The monthly amount of storage and core hours of usage available to students is equivalent to the amount included with {% data variables.product.prodname_pro %} accounts. For more information, see [AUTOTITLE](/billing/managing-billing-for-your-products/managing-billing-for-github-codespaces/about-billing-for-github-codespaces). diff --git a/data/reusables/emus/migration-roles-prereq.md b/data/reusables/emus/migration-roles-prereq.md index 2d754938745c..a704b036d7e7 100644 --- a/data/reusables/emus/migration-roles-prereq.md +++ b/data/reusables/emus/migration-roles-prereq.md @@ -1,4 +1,4 @@ * You'll need to access both your enterprise on {% data variables.product.github %} and your tenant on Entra ID. * To configure the {% data variables.product.prodname_emu_idp_oidc_application %} application on Entra ID, you must sign into the Entra ID tenant as a user with the Global Administrator role. - * To sign in as the setup user for your enterprise on {% data variables.product.github %}, you must use a recovery code for the enterprise. For more information, see "[AUTOTITLE](/admin/identity-and-access-management/managing-recovery-codes-for-your-enterprise/downloading-your-enterprise-accounts-single-sign-on-recovery-codes)." + * To sign in as the setup user for your enterprise on {% data variables.product.github %}, you must use a recovery code for the enterprise. For more information, see [AUTOTITLE](/admin/identity-and-access-management/managing-recovery-codes-for-your-enterprise/downloading-your-enterprise-accounts-single-sign-on-recovery-codes). diff --git a/data/reusables/emus/ssh-ca-support-for-emu.md b/data/reusables/emus/ssh-ca-support-for-emu.md index 049000aa8663..4f3bea44f2ed 100644 --- a/data/reusables/emus/ssh-ca-support-for-emu.md +++ b/data/reusables/emus/ssh-ca-support-for-emu.md @@ -1 +1 @@ -Members cannot use the certificate to access forks of the organization's repositories, unless the enterprise has allowed SSH CAs to access user owned repositories. For more information, see "[AUTOTITLE](/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities)." +Members cannot use the certificate to access forks of the organization's repositories, unless the enterprise has allowed SSH CAs to access user owned repositories. For more information, see [AUTOTITLE](/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities). diff --git a/data/reusables/emus/use-enterprise-recovery-code.md b/data/reusables/emus/use-enterprise-recovery-code.md index 9587b2b17902..faf9a82e0120 100644 --- a/data/reusables/emus/use-enterprise-recovery-code.md +++ b/data/reusables/emus/use-enterprise-recovery-code.md @@ -1,4 +1,4 @@ 1. When prompted to continue to your identity provider, click **Use a recovery code** and sign in using one of your enterprise's recovery codes. > [!NOTE] - > You must use a recovery code for your enterprise, not your user account. For more information, see "[AUTOTITLE](/admin/identity-and-access-management/managing-recovery-codes-for-your-enterprise/downloading-your-enterprise-accounts-single-sign-on-recovery-codes)." + > You must use a recovery code for your enterprise, not your user account. For more information, see [AUTOTITLE](/admin/identity-and-access-management/managing-recovery-codes-for-your-enterprise/downloading-your-enterprise-accounts-single-sign-on-recovery-codes). diff --git a/data/reusables/enterprise-accounts/azure-admin-approval-required-message.md b/data/reusables/enterprise-accounts/azure-admin-approval-required-message.md index 629317462c41..208448283142 100644 --- a/data/reusables/enterprise-accounts/azure-admin-approval-required-message.md +++ b/data/reusables/enterprise-accounts/azure-admin-approval-required-message.md @@ -1 +1 @@ -If you don't see a "Permissions requested" prompt, and instead see a message indicating that you need admin approval, see "[Message: "Need admin approval"](#message-need-admin-approval)." +If you don't see a "Permissions requested" prompt, and instead see a message indicating that you need admin approval, see [Message: "Need admin approval"](#message-need-admin-approval). diff --git a/data/reusables/enterprise-accounts/download-recovery-codes.md b/data/reusables/enterprise-accounts/download-recovery-codes.md index 7fb95cac8db6..9e7ac40b612d 100644 --- a/data/reusables/enterprise-accounts/download-recovery-codes.md +++ b/data/reusables/enterprise-accounts/download-recovery-codes.md @@ -1 +1 @@ -1. To ensure you can still access your enterprise on {% data variables.product.github %} if your IdP is unavailable in the future, click **Download**, **Print**, or **Copy** to save your recovery codes. For more information, see "[AUTOTITLE](/admin/identity-and-access-management/managing-recovery-codes-for-your-enterprise/downloading-your-enterprise-accounts-single-sign-on-recovery-codes)." +1. To ensure you can still access your enterprise on {% data variables.product.github %} if your IdP is unavailable in the future, click **Download**, **Print**, or **Copy** to save your recovery codes. For more information, see [AUTOTITLE](/admin/identity-and-access-management/managing-recovery-codes-for-your-enterprise/downloading-your-enterprise-accounts-single-sign-on-recovery-codes). diff --git a/data/reusables/enterprise-accounts/emu-configure-authentication.md b/data/reusables/enterprise-accounts/emu-configure-authentication.md index 94125d790f46..b9ac6efa3d55 100644 --- a/data/reusables/enterprise-accounts/emu-configure-authentication.md +++ b/data/reusables/enterprise-accounts/emu-configure-authentication.md @@ -8,5 +8,5 @@ Next, configure how your members will authenticate. To get started, read the guide for your chosen authentication method. -* "[AUTOTITLE](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-oidc-for-enterprise-managed-users)" -* "[AUTOTITLE](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-saml-single-sign-on-for-enterprise-managed-users)" +* [AUTOTITLE](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-oidc-for-enterprise-managed-users) +* [AUTOTITLE](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-saml-single-sign-on-for-enterprise-managed-users) diff --git a/data/reusables/enterprise-accounts/emu-configure-provisioning.md b/data/reusables/enterprise-accounts/emu-configure-provisioning.md index 45c4bdb72a38..b4d7ea638dea 100644 --- a/data/reusables/enterprise-accounts/emu-configure-provisioning.md +++ b/data/reusables/enterprise-accounts/emu-configure-provisioning.md @@ -1 +1 @@ -After you configure authentication, you can configure SCIM provisioning, which is how your IdP will create {% data variables.enterprise.prodname_managed_users %} on {% data variables.product.github %}. See "[AUTOTITLE](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-scim-provisioning-for-enterprise-managed-users)." +After you configure authentication, you can configure SCIM provisioning, which is how your IdP will create {% data variables.enterprise.prodname_managed_users %} on {% data variables.product.github %}. See [AUTOTITLE](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-scim-provisioning-for-enterprise-managed-users). diff --git a/data/reusables/enterprise-accounts/emu-create-a-pat.md b/data/reusables/enterprise-accounts/emu-create-a-pat.md index bba0075a7406..b2a71cffeecd 100644 --- a/data/reusables/enterprise-accounts/emu-create-a-pat.md +++ b/data/reusables/enterprise-accounts/emu-create-a-pat.md @@ -4,4 +4,4 @@ Next, create a {% data variables.product.pat_generic %} that you can use to conf * The token must have at least the **scim:enterprise** scope. * The token must have **no expiration**. -To learn how to create a {% data variables.product.pat_v1 %}, see "[AUTOTITLE](/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens)." +To learn how to create a {% data variables.product.pat_v1 %}, see [AUTOTITLE](/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens). diff --git a/data/reusables/enterprise-accounts/emu-manage-org-membership.md b/data/reusables/enterprise-accounts/emu-manage-org-membership.md index b2d0245118d3..b56848957639 100644 --- a/data/reusables/enterprise-accounts/emu-manage-org-membership.md +++ b/data/reusables/enterprise-accounts/emu-manage-org-membership.md @@ -1 +1 @@ -After authentication and provisioning are configured, you can start managing organization membership for your {% data variables.enterprise.prodname_managed_users %} by synchronizing IdP groups with teams. See "[AUTOTITLE](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/managing-team-memberships-with-identity-provider-groups)." +After authentication and provisioning are configured, you can start managing organization membership for your {% data variables.enterprise.prodname_managed_users %} by synchronizing IdP groups with teams. See [AUTOTITLE](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/managing-team-memberships-with-identity-provider-groups). diff --git a/data/reusables/enterprise-accounts/emu-more-info-account.md b/data/reusables/enterprise-accounts/emu-more-info-account.md index 38639f4ffe4e..1d789f83fdbc 100644 --- a/data/reusables/enterprise-accounts/emu-more-info-account.md +++ b/data/reusables/enterprise-accounts/emu-more-info-account.md @@ -1 +1 @@ -For more information, see "[AUTOTITLE](/get-started/learning-about-github/types-of-github-accounts#enterprise-managed-users)." +For more information, see [AUTOTITLE](/get-started/learning-about-github/types-of-github-accounts#enterprise-managed-users). diff --git a/data/reusables/enterprise-accounts/emu-saml-note.md b/data/reusables/enterprise-accounts/emu-saml-note.md index 604f24357fb4..ece315989f7d 100644 --- a/data/reusables/enterprise-accounts/emu-saml-note.md +++ b/data/reusables/enterprise-accounts/emu-saml-note.md @@ -1,6 +1,6 @@ {% ifversion ghec %} > [!NOTE] -> If your enterprise uses {% data variables.product.prodname_emus %}, you must follow a different process to configure SAML single sign-on. For more information, see "[AUTOTITLE](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-saml-single-sign-on-for-enterprise-managed-users)." +> If your enterprise uses {% data variables.product.prodname_emus %}, you must follow a different process to configure SAML single sign-on. For more information, see [AUTOTITLE](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-saml-single-sign-on-for-enterprise-managed-users). {% endif %} diff --git a/data/reusables/enterprise-accounts/emu-scim-note.md b/data/reusables/enterprise-accounts/emu-scim-note.md index a0b66d26eb5d..f8b00faf1294 100644 --- a/data/reusables/enterprise-accounts/emu-scim-note.md +++ b/data/reusables/enterprise-accounts/emu-scim-note.md @@ -1,6 +1,6 @@ {% ifversion ghec %} > [!NOTE] -> If your enterprise uses {% data variables.product.prodname_emus %}, you do not need to use team synchronization. Instead, you can manage team membership via the SCIM configuration you created while setting up your enterprise. For more information, see "[AUTOTITLE](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/managing-team-memberships-with-identity-provider-groups)." +> If your enterprise uses {% data variables.product.prodname_emus %}, you do not need to use team synchronization. Instead, you can manage team membership via the SCIM configuration you created while setting up your enterprise. For more information, see [AUTOTITLE](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/managing-team-memberships-with-identity-provider-groups). {% endif %} diff --git a/data/reusables/enterprise-accounts/emu-short-summary.md b/data/reusables/enterprise-accounts/emu-short-summary.md index d91d145e9822..383693642830 100644 --- a/data/reusables/enterprise-accounts/emu-short-summary.md +++ b/data/reusables/enterprise-accounts/emu-short-summary.md @@ -1 +1 @@ -If you choose to use {% data variables.product.prodname_emus %}, you have increased control over your enterprise's members and resources. With {% data variables.product.prodname_emus %}, all members are provisioned and managed through your identity provider (IdP) instead of users creating their own accounts on {% data variables.product.product_name %}. Organization and team membership can be managed using groups on your IdP. {% data variables.enterprise.prodname_managed_users_caps %} are restricted to their enterprise and are unable to push code, collaborate, or interact with users, repositories, and organizations outside of their enterprise. For more information, see "[AUTOTITLE](/enterprise-cloud@latest/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users){% ifversion not ghec %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %} +If you choose to use {% data variables.product.prodname_emus %}, you have increased control over your enterprise's members and resources. With {% data variables.product.prodname_emus %}, all members are provisioned and managed through your identity provider (IdP) instead of users creating their own accounts on {% data variables.product.product_name %}. Organization and team membership can be managed using groups on your IdP. {% data variables.enterprise.prodname_managed_users_caps %} are restricted to their enterprise and are unable to push code, collaborate, or interact with users, repositories, and organizations outside of their enterprise. For more information, see [AUTOTITLE](/enterprise-cloud@latest/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users){% ifversion not ghec %} in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}.{% endif %} diff --git a/data/reusables/enterprise-accounts/invite-organization.md b/data/reusables/enterprise-accounts/invite-organization.md index 763ed22f7851..e14cb6bd2fe3 100644 --- a/data/reusables/enterprise-accounts/invite-organization.md +++ b/data/reusables/enterprise-accounts/invite-organization.md @@ -1 +1 @@ -Enterprise account owners can invite existing organization accounts to join their enterprise. For more information, see "[AUTOTITLE](/enterprise-cloud@latest/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise#inviting-an-organization-to-join-your-enterprise-account)." +Enterprise account owners can invite existing organization accounts to join their enterprise. For more information, see [AUTOTITLE](/enterprise-cloud@latest/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise#inviting-an-organization-to-join-your-enterprise-account). diff --git a/data/reusables/enterprise-accounts/license-tab.md b/data/reusables/enterprise-accounts/license-tab.md index 5db07109f16f..549a45749235 100644 --- a/data/reusables/enterprise-accounts/license-tab.md +++ b/data/reusables/enterprise-accounts/license-tab.md @@ -1,3 +1,3 @@ 1. Under **{% octicon "gear" aria-hidden="true" %} Settings**, click **{% ifversion ghec %}Licensing{% elsif ghes %}License{% endif %}**. {% ifversion enhanced-billing-platform %} - >[!NOTE] If you are on the enhanced billing platform, the licensing page has been relocated. See "[AUTOTITLE](/billing/using-the-enhanced-billing-platform-for-enterprises/gathering-insights-on-your-spending#viewing-license-usage)."{% endif %} + >[!NOTE] If you are on the enhanced billing platform, the licensing page has been relocated. See [AUTOTITLE](/billing/using-the-enhanced-billing-platform-for-enterprises/gathering-insights-on-your-spending#viewing-license-usage).{% endif %} diff --git a/data/reusables/enterprise-accounts/support-entitlements.md b/data/reusables/enterprise-accounts/support-entitlements.md index 1c8359987234..e4ac240e3402 100644 --- a/data/reusables/enterprise-accounts/support-entitlements.md +++ b/data/reusables/enterprise-accounts/support-entitlements.md @@ -1,6 +1,6 @@ {% ifversion ghec %} -To open, view, and comment on support tickets associated with an enterprise account, you must have support entitlements for the enterprise. Enterprise owners and billing managers automatically have a support entitlement, and enterprise owners can add support entitlements to enterprise members. For more information, see "[AUTOTITLE](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise)." +To open, view, and comment on support tickets associated with an enterprise account, you must have support entitlements for the enterprise. Enterprise owners and billing managers automatically have a support entitlement, and enterprise owners can add support entitlements to enterprise members. For more information, see [AUTOTITLE](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise). > [!NOTE] > Any organization member can create tickets associated with an individual organization that is owned by an enterprise account. Support entitlements are only required to create tickets associated with the enterprise account itself. diff --git a/data/reusables/enterprise-accounts/team-sync-override.md b/data/reusables/enterprise-accounts/team-sync-override.md index 464d5e540315..26c764708328 100644 --- a/data/reusables/enterprise-accounts/team-sync-override.md +++ b/data/reusables/enterprise-accounts/team-sync-override.md @@ -1,3 +1,3 @@ {% ifversion ghec %} -If your organization is owned by an enterprise account, enabling team synchronization for the enterprise account will override your organization-level team synchronization settings. For more information, see "[AUTOTITLE](/admin/identity-and-access-management/using-saml-for-enterprise-iam/managing-team-synchronization-for-organizations-in-your-enterprise)." +If your organization is owned by an enterprise account, enabling team synchronization for the enterprise account will override your organization-level team synchronization settings. For more information, see [AUTOTITLE](/admin/identity-and-access-management/using-saml-for-enterprise-iam/managing-team-synchronization-for-organizations-in-your-enterprise). {% endif %} diff --git a/data/reusables/enterprise-accounts/tenant-app-permissions.md b/data/reusables/enterprise-accounts/tenant-app-permissions.md index 0218bba525d6..5924476e7d6c 100644 --- a/data/reusables/enterprise-accounts/tenant-app-permissions.md +++ b/data/reusables/enterprise-accounts/tenant-app-permissions.md @@ -1 +1 @@ -To select an Azure subscription, you must have owner permissions to the subscription. If the default tenant does not have the right permissions, you may need to specify a different tenant ID. For more information, see "[Prerequisites](/billing/managing-the-plan-for-your-github-account/connecting-an-azure-subscription#prerequisites)" and [Microsoft identity platform and OAuth 2.0 authorization code flow](https://docs.microsoft.com/en-us/azure/active-directory/develop/v2-oauth2-auth-code-flow#request-an-authorization-code) in Microsoft Docs. +To select an Azure subscription, you must have owner permissions to the subscription. If the default tenant does not have the right permissions, you may need to specify a different tenant ID. For more information, see [Prerequisites](/billing/managing-the-plan-for-your-github-account/connecting-an-azure-subscription#prerequisites) and [Microsoft identity platform and OAuth 2.0 authorization code flow](https://docs.microsoft.com/en-us/azure/active-directory/develop/v2-oauth2-auth-code-flow#request-an-authorization-code) in Microsoft Docs. diff --git a/data/reusables/enterprise-licensing/about-license-sync.md b/data/reusables/enterprise-licensing/about-license-sync.md index f3292adb89bf..98b7d7afce01 100644 --- a/data/reusables/enterprise-licensing/about-license-sync.md +++ b/data/reusables/enterprise-licensing/about-license-sync.md @@ -1 +1 @@ -For a person using multiple {% data variables.product.prodname_enterprise %} environments to only consume a single license, you must synchronize license usage between environments. Then, {% data variables.product.company_short %} will deduplicate users based on the email addresses associated with their user accounts. {% data variables.product.company_short %} deduplicates licenses for the {% data variables.product.prodname_enterprise %} plan itself, {% ifversion ghas-in-license-sync %}and{% ifversion ghec %} if you use {% data variables.product.prodname_ghe_server %} version 3.12 or later,{% endif %} for {% data variables.product.prodname_GH_advanced_security %}{% else %}but not for other {% data variables.product.company_short %} products{% endif %}. For more information, see "[AUTOTITLE](/billing/managing-your-license-for-github-enterprise/troubleshooting-license-usage-for-github-enterprise#about-the-calculation-of-consumed-licenses)." +For a person using multiple {% data variables.product.prodname_enterprise %} environments to only consume a single license, you must synchronize license usage between environments. Then, {% data variables.product.company_short %} will deduplicate users based on the email addresses associated with their user accounts. {% data variables.product.company_short %} deduplicates licenses for the {% data variables.product.prodname_enterprise %} plan itself, {% ifversion ghas-in-license-sync %}and{% ifversion ghec %} if you use {% data variables.product.prodname_ghe_server %} version 3.12 or later,{% endif %} for {% data variables.product.prodname_GH_advanced_security %}{% else %}but not for other {% data variables.product.company_short %} products{% endif %}. For more information, see [AUTOTITLE](/billing/managing-your-license-for-github-enterprise/troubleshooting-license-usage-for-github-enterprise#about-the-calculation-of-consumed-licenses). diff --git a/data/reusables/enterprise-licensing/verified-domains-license-sync.md b/data/reusables/enterprise-licensing/verified-domains-license-sync.md index 57f2185c4a45..19b54f131c55 100644 --- a/data/reusables/enterprise-licensing/verified-domains-license-sync.md +++ b/data/reusables/enterprise-licensing/verified-domains-license-sync.md @@ -1 +1 @@ -> [!NOTE] To make troubleshooting easier, if you synchronize license usage and do not use {% data variables.product.prodname_emus %}, we highly recommend enabling verified domains for your enterprise account on {% data variables.product.prodname_ghe_cloud %}. See "[AUTOTITLE](/enterprise-cloud@latest/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise){% ifversion not ghec %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %} +> [!NOTE] To make troubleshooting easier, if you synchronize license usage and do not use {% data variables.product.prodname_emus %}, we highly recommend enabling verified domains for your enterprise account on {% data variables.product.prodname_ghe_cloud %}. See [AUTOTITLE](/enterprise-cloud@latest/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise){% ifversion not ghec %} in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}.{% endif %} diff --git a/data/reusables/enterprise-licensing/view-consumed-licenses.md b/data/reusables/enterprise-licensing/view-consumed-licenses.md index 8e761a485bb6..4dd4a95eac4b 100644 --- a/data/reusables/enterprise-licensing/view-consumed-licenses.md +++ b/data/reusables/enterprise-licensing/view-consumed-licenses.md @@ -1 +1 @@ -After you synchronize license usage, you can see a report of consumed licenses across all your environments in the enterprise settings on {% data variables.product.prodname_ghe_cloud %}. For more information, see "[AUTOTITLE](/enterprise-cloud@latest/billing/managing-your-license-for-github-enterprise/viewing-license-usage-for-github-enterprise)." +After you synchronize license usage, you can see a report of consumed licenses across all your environments in the enterprise settings on {% data variables.product.prodname_ghe_cloud %}. For more information, see [AUTOTITLE](/enterprise-cloud@latest/billing/managing-your-license-for-github-enterprise/viewing-license-usage-for-github-enterprise). diff --git a/data/reusables/enterprise-managed/assigning-roles.md b/data/reusables/enterprise-managed/assigning-roles.md index c5e787bc27c2..486872a910bc 100644 --- a/data/reusables/enterprise-managed/assigning-roles.md +++ b/data/reusables/enterprise-managed/assigning-roles.md @@ -1 +1 @@ -When assigning users, you can use the "Roles" attribute in the application on your IdP to set a user's role in your enterprise on {% data variables.product.product_name %}. For more information about the roles available to assign, see "[AUTOTITLE](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise)." +When assigning users, you can use the "Roles" attribute in the application on your IdP to set a user's role in your enterprise on {% data variables.product.product_name %}. For more information about the roles available to assign, see [AUTOTITLE](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise). diff --git a/data/reusables/enterprise-managed/emu-prerequisite.md b/data/reusables/enterprise-managed/emu-prerequisite.md index 2d0eac97f26c..28c5fb80b614 100644 --- a/data/reusables/enterprise-managed/emu-prerequisite.md +++ b/data/reusables/enterprise-managed/emu-prerequisite.md @@ -1 +1 @@ -When you began using {% data variables.product.product_name %}, you must have chosen to create an {% data variables.enterprise.prodname_emu_enterprise %}. For more information, see "[AUTOTITLE](/admin/identity-and-access-management/understanding-iam-for-enterprises/identifying-the-best-authentication-method-for-your-enterprise)." +When you began using {% data variables.product.product_name %}, you must have chosen to create an {% data variables.enterprise.prodname_emu_enterprise %}. For more information, see [AUTOTITLE](/admin/identity-and-access-management/understanding-iam-for-enterprises/identifying-the-best-authentication-method-for-your-enterprise). diff --git a/data/reusables/enterprise-managed/repo-collaborators-note.md b/data/reusables/enterprise-managed/repo-collaborators-note.md index 03d03aa18748..cdeb80a437ba 100644 --- a/data/reusables/enterprise-managed/repo-collaborators-note.md +++ b/data/reusables/enterprise-managed/repo-collaborators-note.md @@ -1,3 +1,3 @@ {% ifversion repository-collaborators %} ->[!NOTE] If your enterprise uses {% data variables.enterprise.prodname_managed_users %}, the outside collaborator role is called "repository collaborator." Generally, the documentation for outside collaborators also applies to repository collaborators. For the distinctions that apply, see "[AUTOTITLE](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#outside-collaborators-or-repository-collaborators)." +>[!NOTE] If your enterprise uses {% data variables.enterprise.prodname_managed_users %}, the outside collaborator role is called "repository collaborator." Generally, the documentation for outside collaborators also applies to repository collaborators. For the distinctions that apply, see [AUTOTITLE](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#outside-collaborators-or-repository-collaborators). {% endif %} diff --git a/data/reusables/enterprise-migration-tool/about-the-migrator-role.md b/data/reusables/enterprise-migration-tool/about-the-migrator-role.md index 44f30254d626..eab4b9f5d54a 100644 --- a/data/reusables/enterprise-migration-tool/about-the-migrator-role.md +++ b/data/reusables/enterprise-migration-tool/about-the-migrator-role.md @@ -3,10 +3,10 @@ To remove the need for organization owners to complete migrations, {% data varia Granting the migrator role allows you to designate other teams or individuals to handle your migrations. * You can only grant the migrator role for an organization on {% data variables.product.prodname_dotcom_the_website %} or {% data variables.enterprise.data_residency_site %}. -* You can grant the migrator role to an individual user or a team. We strongly recommend that you assign the migrator role to a team. Then, you can further customize who can run a migration by adjusting team membership. See "[AUTOTITLE](/organizations/organizing-members-into-teams/adding-organization-members-to-a-team)" or "[AUTOTITLE](/organizations/organizing-members-into-teams/removing-organization-members-from-a-team)." +* You can grant the migrator role to an individual user or a team. We strongly recommend that you assign the migrator role to a team. Then, you can further customize who can run a migration by adjusting team membership. See [AUTOTITLE](/organizations/organizing-members-into-teams/adding-organization-members-to-a-team) or [AUTOTITLE](/organizations/organizing-members-into-teams/removing-organization-members-from-a-team). * The migrator must use a {% data variables.product.pat_generic %} that meets all the requirements for running migrations. > [!WARNING] > When you grant the migrator role in an organization to a user or team, you are granting them the ability to import or export any repository in that organization. -To grant the migrator role, see "[Granting the migrator role](#granting-the-migrator-role)." +To grant the migrator role, see [Granting the migrator role](#granting-the-migrator-role). diff --git a/data/reusables/enterprise-migration-tool/blob-storage-management-console.md b/data/reusables/enterprise-migration-tool/blob-storage-management-console.md index 606ed356250f..4e5e27a6dea8 100644 --- a/data/reusables/enterprise-migration-tool/blob-storage-management-console.md +++ b/data/reusables/enterprise-migration-tool/blob-storage-management-console.md @@ -9,7 +9,7 @@ After you set up an AWS S3 storage bucket or Azure Blob Storage storage account, 1. Optionally, to import storage settings you configured for {% data variables.product.prodname_actions %}, select **Copy Storage settings from Actions**. For more information see, "[Enabling GitHub Actions with Azure Blob storage]({% ifversion not ghes %}/enterprise-server@latest{% endif %}/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-azure-blob-storage)" and "[Enabling GitHub Actions with Amazon S3 storage]({% ifversion not ghes %}/enterprise-server@latest{% endif %}/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-amazon-s3-storage)." > [!NOTE] - > After copying your storage settings, you may still need to update the configuration of your cloud storage account to work with {% data variables.product.prodname_importer_proper_name %}. In particular, you must ensure that {% data variables.product.prodname_dotcom %}'s IP addresses are allowlisted. For more information, see "[AUTOTITLE](/migrations/using-github-enterprise-importer/migrating-between-github-products/managing-access-for-a-migration-between-github-products#configuring-ip-allow-lists-for-migrations)." + > After copying your storage settings, you may still need to update the configuration of your cloud storage account to work with {% data variables.product.prodname_importer_proper_name %}. In particular, you must ensure that {% data variables.product.prodname_dotcom %}'s IP addresses are allowlisted. For more information, see [AUTOTITLE](/migrations/using-github-enterprise-importer/migrating-between-github-products/managing-access-for-a-migration-between-github-products#configuring-ip-allow-lists-for-migrations). 1. If you do not import storage settings from {% data variables.product.prodname_actions %}, select either **Azure Blob Storage** or **Amazon S3** and fill in the required details. diff --git a/data/reusables/enterprise-migration-tool/branch-protection-migration.md b/data/reusables/enterprise-migration-tool/branch-protection-migration.md index bd0ad5d43fec..fa4029521a63 100644 --- a/data/reusables/enterprise-migration-tool/branch-protection-migration.md +++ b/data/reusables/enterprise-migration-tool/branch-protection-migration.md @@ -1,4 +1,4 @@ -Branch protections apply a specified set of rules to a specific branch name or branch name pattern. For more information, see "[AUTOTITLE](/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/about-protected-branches)." +Branch protections apply a specified set of rules to a specific branch name or branch name pattern. For more information, see [AUTOTITLE](/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/about-protected-branches). Branch protections will always be migrated, but certain rules will not be migrated. The following branch protection rules are not migrated. diff --git a/data/reusables/enterprise-migration-tool/checking-the-migration-status.md b/data/reusables/enterprise-migration-tool/checking-the-migration-status.md index d816ccdd5422..feadc3c248a9 100644 --- a/data/reusables/enterprise-migration-tool/checking-the-migration-status.md +++ b/data/reusables/enterprise-migration-tool/checking-the-migration-status.md @@ -11,4 +11,4 @@ The way you check the status of your migration depends on how you ran the migrat * If you ran the migration using the {% data variables.product.prodname_cli %} with the optional `--queue-only` argument, the process will exit immediately after queueing the migration, and will not tell you if the migration succeeded or failed. You can check a migration's status using the `wait-for-migration` command, or by reviewing the migration log. * If you ran the migration using the GraphQL API, you can query the `state` and `failureReason` fields on the `RepositoryMigration` object. -If the migration failed, the migration log may contain additional information about the cause of the failure. For more information, see "[Reviewing the migration log](#reviewing-the-migration-log)." +If the migration failed, the migration log may contain additional information about the cause of the failure. For more information, see [Reviewing the migration log](#reviewing-the-migration-log). diff --git a/data/reusables/enterprise-migration-tool/configuring-ip-allow-lists.md b/data/reusables/enterprise-migration-tool/configuring-ip-allow-lists.md index e0f23a5b00b0..b24a43f9d847 100644 --- a/data/reusables/enterprise-migration-tool/configuring-ip-allow-lists.md +++ b/data/reusables/enterprise-migration-tool/configuring-ip-allow-lists.md @@ -1,4 +1,4 @@ -If the source or destination of your migration uses an IP allow list (either {% data variables.product.company_short %}'s IP allow list feature or your identity provider's (IdP) IP allow list restrictions, such as Azure CAP), you need to configure IP allow lists on {% data variables.product.prodname_dotcom %}. See "[AUTOTITLE](/enterprise-cloud@latest/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-allowed-ip-addresses-for-your-organization)" and "[AUTOTITLE](/enterprise-cloud@latest/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise-with-an-ip-allow-list)." +If the source or destination of your migration uses an IP allow list (either {% data variables.product.company_short %}'s IP allow list feature or your identity provider's (IdP) IP allow list restrictions, such as Azure CAP), you need to configure IP allow lists on {% data variables.product.prodname_dotcom %}. See [AUTOTITLE](/enterprise-cloud@latest/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-allowed-ip-addresses-for-your-organization) and [AUTOTITLE](/enterprise-cloud@latest/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise-with-an-ip-allow-list). * If you use {% data variables.product.company_short %}'s IP allow list feature, you must add the {% data variables.product.prodname_dotcom %} IP ranges below to the allow list for the source and/or destination organizations. * If you use your IdP's IP allow list to restrict access to your enterprise on {% data variables.product.prodname_dotcom %}, you should disable these restrictions in your enterprise account settings until after your migration is complete. diff --git a/data/reusables/enterprise-migration-tool/create-pats.md b/data/reusables/enterprise-migration-tool/create-pats.md index 57d483be0b15..ccbf114e2461 100644 --- a/data/reusables/enterprise-migration-tool/create-pats.md +++ b/data/reusables/enterprise-migration-tool/create-pats.md @@ -1,2 +1,2 @@ -1. Create and record a {% data variables.product.pat_v1 %} that will authenticate for the destination organization on {% data variables.product.prodname_ghe_cloud %}, making sure that the token meets all requirements. For more information, see "[AUTOTITLE](/migrations/using-github-enterprise-importer/migrating-between-github-products/managing-access-for-a-migration-between-github-products#creating-a-personal-access-token-for-github-enterprise-importer)." +1. Create and record a {% data variables.product.pat_v1 %} that will authenticate for the destination organization on {% data variables.product.prodname_ghe_cloud %}, making sure that the token meets all requirements. For more information, see [AUTOTITLE](/migrations/using-github-enterprise-importer/migrating-between-github-products/managing-access-for-a-migration-between-github-products#creating-a-personal-access-token-for-github-enterprise-importer). 1. Create and record a {% data variables.product.pat_generic %} that will authenticate for the source organization, making sure that this token also meets all of the same requirements. diff --git a/data/reusables/enterprise-migration-tool/creating-a-pat-steps.md b/data/reusables/enterprise-migration-tool/creating-a-pat-steps.md index 52bfd3af442b..838e363ce3fd 100644 --- a/data/reusables/enterprise-migration-tool/creating-a-pat-steps.md +++ b/data/reusables/enterprise-migration-tool/creating-a-pat-steps.md @@ -1,3 +1,3 @@ -1. Verify that you have a sufficient role for the task you want to complete. For more information, see "[Required roles](#required-roles)." -1. Create a {% data variables.product.pat_v1 %}, making sure to grant all the scopes required for the task you want to complete. {% data reusables.user-settings.generic-classic-pat-only %} For more information, "[AUTOTITLE](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)" and "[Required scopes for {% data variables.product.pat_generic %}](#required-scopes-for-personal-access-tokens)." -1. If SAML single sign-on is enforced for the organization(s) you need to access, authorize the {% data variables.product.pat_generic %} for SSO. For more information, see "[AUTOTITLE](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)." +1. Verify that you have a sufficient role for the task you want to complete. For more information, see [Required roles](#required-roles). +1. Create a {% data variables.product.pat_v1 %}, making sure to grant all the scopes required for the task you want to complete. {% data reusables.user-settings.generic-classic-pat-only %} For more information, [AUTOTITLE](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token) and [Required scopes for {% data variables.product.pat_generic %}](#required-scopes-for-personal-access-tokens). +1. If SAML single sign-on is enforced for the organization(s) you need to access, authorize the {% data variables.product.pat_generic %} for SSO. For more information, see [AUTOTITLE](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on). diff --git a/data/reusables/enterprise-migration-tool/data-not-migrated.md b/data/reusables/enterprise-migration-tool/data-not-migrated.md index 9a13349c963f..a58b4be6dbac 100644 --- a/data/reusables/enterprise-migration-tool/data-not-migrated.md +++ b/data/reusables/enterprise-migration-tool/data-not-migrated.md @@ -5,14 +5,14 @@ * {% data variables.product.prodname_dependabot %} secrets * Discussions at the repository level * Edit history of issue comments and pull request comments -* Fork relationships between repositories (see "[AUTOTITLE](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)") +* Fork relationships between repositories (see [AUTOTITLE](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)) * {% data variables.product.prodname_actions %} secrets, variables, environments, self-hosted runners, {% data variables.actions.hosted_runner %}s, or workflow run history * GitHub Apps and GitHub App installations -* {% data variables.large_files.product_name_short %} objects and large binaries (repositories using {% data variables.large_files.product_name_short %} are still supported, see "[Limitations of {% data variables.product.prodname_importer_proper_name %}](#limitations-of-github-enterprise-importer)") +* {% data variables.large_files.product_name_short %} objects and large binaries (repositories using {% data variables.large_files.product_name_short %} are still supported, see [Limitations of {% data variables.product.prodname_importer_proper_name %}](#limitations-of-github-enterprise-importer)) * Packages in {% data variables.product.prodname_registry %} * Projects (classic) at the organization level * {% data variables.product.prodname_projects_v2 %} (the new projects experience) -* References between pull requests and issues in different repositories (see "[AUTOTITLE](/get-started/writing-on-github/working-with-advanced-formatting/autolinked-references-and-urls)") +* References between pull requests and issues in different repositories (see [AUTOTITLE](/get-started/writing-on-github/working-with-advanced-formatting/autolinked-references-and-urls)) * Remediation states of {% data variables.product.prodname_secret_scanning %} results * Repositories owned by user accounts{% ifversion repository-properties %} * Repository properties{% endif %} diff --git a/data/reusables/enterprise-migration-tool/deploy-key-bypass.md b/data/reusables/enterprise-migration-tool/deploy-key-bypass.md index 28ada4675f88..6d7e8d5b20f8 100644 --- a/data/reusables/enterprise-migration-tool/deploy-key-bypass.md +++ b/data/reusables/enterprise-migration-tool/deploy-key-bypass.md @@ -1,3 +1,3 @@ > [!NOTE] If the repository you are migrating has rulesets that the incoming repository doesn't match, the migration will be blocked. To bypass these rulesets and allow the migration, you can apply a ruleset bypass for all deploy keys in the target organization. > -> Repository rulesets can be set at the organization level. If the incoming repository does not match any of these rulesets, you will need to use the deploy key bypass for each one. See "[AUTOTITLE](/organizations/managing-organization-settings/creating-rulesets-for-repositories-in-your-organization#granting-bypass-permissions-for-your-branch-or-tag-ruleset)." +> Repository rulesets can be set at the organization level. If the incoming repository does not match any of these rulesets, you will need to use the deploy key bypass for each one. See [AUTOTITLE](/organizations/managing-organization-settings/creating-rulesets-for-repositories-in-your-organization#granting-bypass-permissions-for-your-branch-or-tag-ruleset). diff --git a/data/reusables/enterprise-migration-tool/download-migration-logs-flag.md b/data/reusables/enterprise-migration-tool/download-migration-logs-flag.md index 587adbfd3b0c..b1aea01b623e 100644 --- a/data/reusables/enterprise-migration-tool/download-migration-logs-flag.md +++ b/data/reusables/enterprise-migration-tool/download-migration-logs-flag.md @@ -1 +1 @@ -If you want the script to download the migration log for each migrated repository, add the `--download-migration-logs` flag. For more information about migration logs, see "[AUTOTITLE](/migrations/using-github-enterprise-importer/completing-your-migration-with-github-enterprise-importer/accessing-your-migration-logs-for-github-enterprise-importer#downloading-all-migration-logs-for-an-organization)." +If you want the script to download the migration log for each migrated repository, add the `--download-migration-logs` flag. For more information about migration logs, see [AUTOTITLE](/migrations/using-github-enterprise-importer/completing-your-migration-with-github-enterprise-importer/accessing-your-migration-logs-for-github-enterprise-importer#downloading-all-migration-logs-for-an-organization). diff --git a/data/reusables/enterprise-migration-tool/extra-requirements-storage.md b/data/reusables/enterprise-migration-tool/extra-requirements-storage.md index 728fd5e7550f..1505d3276f48 100644 --- a/data/reusables/enterprise-migration-tool/extra-requirements-storage.md +++ b/data/reusables/enterprise-migration-tool/extra-requirements-storage.md @@ -1,2 +1,2 @@ -* You must allow access to the egress IP ranges for {% data variables.enterprise.data_residency_site %}. See "[AUTOTITLE](/enterprise-cloud@latest/admin/data-residency/network-details-for-ghecom#ranges-for-egress-traffic)." +* You must allow access to the egress IP ranges for {% data variables.enterprise.data_residency_site %}. See [AUTOTITLE](/enterprise-cloud@latest/admin/data-residency/network-details-for-ghecom#ranges-for-egress-traffic). * If you're using Azure Blob Storage, you may need to perform some additional configuration. Please contact {% data variables.contact.contact_support_page %}. diff --git a/data/reusables/enterprise-migration-tool/github-pat-required-scopes.md b/data/reusables/enterprise-migration-tool/github-pat-required-scopes.md index 1a1e3775ae44..d886ebe1a3d1 100644 --- a/data/reusables/enterprise-migration-tool/github-pat-required-scopes.md +++ b/data/reusables/enterprise-migration-tool/github-pat-required-scopes.md @@ -1,7 +1,7 @@ The scopes that are required for your {% data variables.product.prodname_dotcom %} {% data variables.product.pat_v1 %} depend on your role and the task you want to complete. > [!NOTE] -> {% data reusables.user-settings.generic-classic-pat-only %} This means that you cannot use {% data variables.product.prodname_importer_proper_name %} if your organization uses the "Restrict {% data variables.product.pat_v1_plural %} from accessing your organizations" policy. For more information, see "[AUTOTITLE](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-personal-access-tokens-in-your-enterprise#restricting-access-by-personal-access-tokens)." +> {% data reusables.user-settings.generic-classic-pat-only %} This means that you cannot use {% data variables.product.prodname_importer_proper_name %} if your organization uses the "Restrict {% data variables.product.pat_v1_plural %} from accessing your organizations" policy. For more information, see [AUTOTITLE](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-personal-access-tokens-in-your-enterprise#restricting-access-by-personal-access-tokens). Task | Organization owner | Migrator ---- | -------- | ----- | diff --git a/data/reusables/enterprise-migration-tool/github-trial-prerequisite.md b/data/reusables/enterprise-migration-tool/github-trial-prerequisite.md index bbfb5f056e71..a3ba03b72964 100644 --- a/data/reusables/enterprise-migration-tool/github-trial-prerequisite.md +++ b/data/reusables/enterprise-migration-tool/github-trial-prerequisite.md @@ -1 +1 @@ -We strongly recommend that you perform a trial run of your migration and complete your production migration soon after. To learn more about trial runs, see "[AUTOTITLE](/migrations/using-github-enterprise-importer/migrating-between-github-products/overview-of-a-migration-between-github-products#running-your-migrations)." +We strongly recommend that you perform a trial run of your migration and complete your production migration soon after. To learn more about trial runs, see [AUTOTITLE](/migrations/using-github-enterprise-importer/migrating-between-github-products/overview-of-a-migration-between-github-products#running-your-migrations). diff --git a/data/reusables/enterprise-migration-tool/grant-migrator-role-graphql.md b/data/reusables/enterprise-migration-tool/grant-migrator-role-graphql.md index a826086e4881..2886fde305a5 100644 --- a/data/reusables/enterprise-migration-tool/grant-migrator-role-graphql.md +++ b/data/reusables/enterprise-migration-tool/grant-migrator-role-graphql.md @@ -1,6 +1,6 @@ You can use the `grantMigratorRole` GraphQL mutation to assign the migrator role and the `revokeMigratorRole` mutation to revoke the migrator role. -You must use a {% data variables.product.pat_generic %} (PAT) that meets all access requirements. For more information, see the "[Required scopes for {% data variables.product.pat_generic %}s](#required-scopes-for-personal-access-tokens)." +You must use a {% data variables.product.pat_generic %} (PAT) that meets all access requirements. For more information, see the [Required scopes for {% data variables.product.pat_generic %}s](#required-scopes-for-personal-access-tokens). #### `grantMigratorRole` mutation diff --git a/data/reusables/enterprise-migration-tool/identifying-githubs-ip-ranges.md b/data/reusables/enterprise-migration-tool/identifying-githubs-ip-ranges.md index 85329843d101..a541971bc0be 100644 --- a/data/reusables/enterprise-migration-tool/identifying-githubs-ip-ranges.md +++ b/data/reusables/enterprise-migration-tool/identifying-githubs-ip-ranges.md @@ -13,4 +13,4 @@ You can get an up-to-date list of IP ranges used by {% data variables.product.pr The `github_enterprise_importer` key in the response contains a list of IP ranges used for migrations. -For more information, see "[AUTOTITLE](/rest/meta#get-github-meta-information)." +For more information, see [AUTOTITLE](/rest/meta#get-github-meta-information). diff --git a/data/reusables/enterprise-migration-tool/install-gei-extension-intro.md b/data/reusables/enterprise-migration-tool/install-gei-extension-intro.md index 73e6d976dd63..a9acf697328c 100644 --- a/data/reusables/enterprise-migration-tool/install-gei-extension-intro.md +++ b/data/reusables/enterprise-migration-tool/install-gei-extension-intro.md @@ -1 +1 @@ -If this is your first migration, you'll need to install the {% data variables.product.prodname_gei_cli %}. For more information about the {% data variables.product.prodname_cli %}, see "[AUTOTITLE](/github-cli/github-cli/about-github-cli)." +If this is your first migration, you'll need to install the {% data variables.product.prodname_gei_cli %}. For more information about the {% data variables.product.prodname_cli %}, see [AUTOTITLE](/github-cli/github-cli/about-github-cli). diff --git a/data/reusables/enterprise-migration-tool/limitations-of-migrated-data.md b/data/reusables/enterprise-migration-tool/limitations-of-migrated-data.md index 14c85b86cecd..c0a31bc05471 100644 --- a/data/reusables/enterprise-migration-tool/limitations-of-migrated-data.md +++ b/data/reusables/enterprise-migration-tool/limitations-of-migrated-data.md @@ -4,14 +4,14 @@ There are limits to what {% data variables.product.prodname_importer_proper_name * **2 GB size limit for a single Git commit:** No single commit in your Git repository can be larger than 2 GB. If any of your commits are larger than 2 GB, you will need to split the commit into smaller commits that are each 2 GB or smaller. * **255 byte limit for Git references:** No single [Git reference](https://git-scm.com/book/en/v2/Git-Internals-Git-References), commonly known as a "ref", can have a name larger than 255 bytes. Usually, this means that your references cannot be more than 255 characters long, but any non-[ASCII](https://en.wikipedia.org/wiki/ASCII) characters, such as emojis, may consume more than one byte. If any of your Git references are too large, we'll return a clear error message. -* **100 MB file size limit:** No single file in your Git repository can be larger than 100 MB. Consider using {% data variables.large_files.product_name_short %} for storing large files. For more information, see "[AUTOTITLE](/repositories/working-with-files/managing-large-files)." +* **100 MB file size limit:** No single file in your Git repository can be larger than 100 MB. Consider using {% data variables.large_files.product_name_short %} for storing large files. For more information, see [AUTOTITLE](/repositories/working-with-files/managing-large-files). ### Limitations of {% data variables.product.prodname_importer_proper_name %} * **10 GB size limit for a Git repository:** This limit only applies to the source code. To check if the repository archive is over the limit, use the [git-sizer](https://github.com/github/git-sizer) tool and review the total blob size in the output. The git-sizer tool also helps to identify potential issues related to large files, blob size, commit size, and tree counts that could impact migrations. * **10 GB limit for metadata:** The {% data variables.product.prodname_importer_secondary_name %} cannot migrate repositories with more than 10 GB of metadata. Metadata includes issues, pull requests, releases, and attachments. In most cases, large metadata is caused by binary assets attached to releases. You can exclude releases from the migration with the `migrate-repo` command's `--skip-releases` flag, and then move your releases manually after the migration. -* **{% data variables.large_files.product_name_short %} objects not migrated:** The {% data variables.product.prodname_importer_secondary_name %} can migrate repositories that use {% data variables.large_files.product_name_short %}, but the LFS objects themselves will not be migrated. They can be pushed to your migration destination as a follow-up task after the migration is complete. For more information, see "[AUTOTITLE](/repositories/creating-and-managing-repositories/duplicating-a-repository#mirroring-a-repository-that-contains-git-large-file-storage-objects)." -* **Follow-up tasks required:** When migrating between {% data variables.product.prodname_dotcom %} products, certain settings are not migrated and must be reconfigured in the new repository. For a list of follow-up tasks you'll need to complete after each migration, see "[AUTOTITLE](/migrations/using-github-enterprise-importer/migrating-between-github-products/overview-of-a-migration-between-github-products#completing-follow-up-tasks)." +* **{% data variables.large_files.product_name_short %} objects not migrated:** The {% data variables.product.prodname_importer_secondary_name %} can migrate repositories that use {% data variables.large_files.product_name_short %}, but the LFS objects themselves will not be migrated. They can be pushed to your migration destination as a follow-up task after the migration is complete. For more information, see [AUTOTITLE](/repositories/creating-and-managing-repositories/duplicating-a-repository#mirroring-a-repository-that-contains-git-large-file-storage-objects). +* **Follow-up tasks required:** When migrating between {% data variables.product.prodname_dotcom %} products, certain settings are not migrated and must be reconfigured in the new repository. For a list of follow-up tasks you'll need to complete after each migration, see [AUTOTITLE](/migrations/using-github-enterprise-importer/migrating-between-github-products/overview-of-a-migration-between-github-products#completing-follow-up-tasks). * **Delayed code search functionality:** Re-indexing the search index can take a few hours after a repository is migrated, and code searches may return unexpected results until re-indexing is complete. -* **Rulesets configured for your organization can cause migrations to fail:** For example, if you configured a rule that requires email addresses for commit authors to end with `@monalisa.cat`, and the repository you're migrating contains commits that don't comply with this rule, your migration will fail. For more information about rulesets, see "[AUTOTITLE](/enterprise-cloud@latest/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/about-rulesets)." -* **Mannequin content might not be searchable:** Mannequins are placeholder users to which imported content (such as issues, pull requests, comments, etc.) is associated. When you search for content associated with a mannequin, such as assigned issues, the issues may not be found. Once a mannequin is reclaimed, the content should be found via the new owner. For more information, see "[AUTOTITLE](/migrations/using-github-enterprise-importer/completing-your-migration-with-github-enterprise-importer/reclaiming-mannequins-for-github-enterprise-importer)." +* **Rulesets configured for your organization can cause migrations to fail:** For example, if you configured a rule that requires email addresses for commit authors to end with `@monalisa.cat`, and the repository you're migrating contains commits that don't comply with this rule, your migration will fail. For more information about rulesets, see [AUTOTITLE](/enterprise-cloud@latest/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/about-rulesets). +* **Mannequin content might not be searchable:** Mannequins are placeholder users to which imported content (such as issues, pull requests, comments, etc.) is associated. When you search for content associated with a mannequin, such as assigned issues, the issues may not be found. Once a mannequin is reclaimed, the content should be found via the new owner. For more information, see [AUTOTITLE](/migrations/using-github-enterprise-importer/completing-your-migration-with-github-enterprise-importer/reclaiming-mannequins-for-github-enterprise-importer). diff --git a/data/reusables/enterprise-migration-tool/migration-query-method.md b/data/reusables/enterprise-migration-tool/migration-query-method.md index 84d64ed71266..f1fbf7c5570b 100644 --- a/data/reusables/enterprise-migration-tool/migration-query-method.md +++ b/data/reusables/enterprise-migration-tool/migration-query-method.md @@ -1,5 +1,5 @@ To make GraphQL queries, you'll need to write your own scripts or use an HTTP client like [Insomnia](https://insomnia.rest/). -To learn more about getting started with the {% data variables.product.prodname_dotcom %} GraphQL API, including how to authenticate, see "[AUTOTITLE](/graphql/guides/forming-calls-with-graphql)." +To learn more about getting started with the {% data variables.product.prodname_dotcom %} GraphQL API, including how to authenticate, see [AUTOTITLE](/graphql/guides/forming-calls-with-graphql). You will send all GraphQL queries to the **destination** of your migration. If you're migrating to {% data variables.enterprise.data_residency %}, make sure to send queries to the endpoint for your enterprise's subdomain of {% data variables.enterprise.data_residency_site %}. diff --git a/data/reusables/enterprise-migration-tool/path-to-key-placeholder.md b/data/reusables/enterprise-migration-tool/path-to-key-placeholder.md index 23b893557ac5..8a0510750e72 100644 --- a/data/reusables/enterprise-migration-tool/path-to-key-placeholder.md +++ b/data/reusables/enterprise-migration-tool/path-to-key-placeholder.md @@ -1 +1 @@ -PATH-TO-KEY | If your Bitbucket Server instance runs on Linux, the path to your SSH private key, such as `~/.ssh/id_rsa`. For SSH key requirements, see "[AUTOTITLE](/migrations/using-github-enterprise-importer/migrating-from-bitbucket-server-to-github-enterprise-cloud/managing-access-for-a-migration-from-bitbucket-server#required-permissions-for-bitbucket-server)". +PATH-TO-KEY | If your Bitbucket Server instance runs on Linux, the path to your SSH private key, such as `~/.ssh/id_rsa`. For SSH key requirements, see [AUTOTITLE](/migrations/using-github-enterprise-importer/migrating-from-bitbucket-server-to-github-enterprise-cloud/managing-access-for-a-migration-from-bitbucket-server#required-permissions-for-bitbucket-server). diff --git a/data/reusables/enterprise-migration-tool/reclaiming-mannequins.md b/data/reusables/enterprise-migration-tool/reclaiming-mannequins.md index d2b25c79f7b4..33cbb84151ef 100644 --- a/data/reusables/enterprise-migration-tool/reclaiming-mannequins.md +++ b/data/reusables/enterprise-migration-tool/reclaiming-mannequins.md @@ -1,6 +1,6 @@ {% data reusables.enterprise-migration-tool.about-mannequins %} -{% data reusables.enterprise-migration-tool.how-to-reclaim %} For more information, see "[AUTOTITLE](/migrations/using-github-enterprise-importer/completing-your-migration-with-github-enterprise-importer/reclaiming-mannequins-for-github-enterprise-importer)." +{% data reusables.enterprise-migration-tool.how-to-reclaim %} For more information, see [AUTOTITLE](/migrations/using-github-enterprise-importer/completing-your-migration-with-github-enterprise-importer/reclaiming-mannequins-for-github-enterprise-importer). > [!NOTE] > Only organization owners can reclaim mannequins. If you've been granted the migrator role, contact an organization owner to perform this step. @@ -8,4 +8,4 @@ 1. Decide if you want to reclaim mannequins. 1. Plan when you'll complete reclaims. 1. Reclaim mannequins. -1. If any of the members do not already have appropriate access to the repository via team membership, give the members access to the repository. For more information, see "[AUTOTITLE](/organizations/managing-user-access-to-your-organizations-repositories/managing-repository-roles/managing-an-individuals-access-to-an-organization-repository)." +1. If any of the members do not already have appropriate access to the repository via team membership, give the members access to the repository. For more information, see [AUTOTITLE](/organizations/managing-user-access-to-your-organizations-repositories/managing-repository-roles/managing-an-individuals-access-to-an-organization-repository). diff --git a/data/reusables/enterprise-migration-tool/reviewing-the-migration-log.md b/data/reusables/enterprise-migration-tool/reviewing-the-migration-log.md index d72fe40c99a1..1939adae22e4 100644 --- a/data/reusables/enterprise-migration-tool/reviewing-the-migration-log.md +++ b/data/reusables/enterprise-migration-tool/reviewing-the-migration-log.md @@ -1,7 +1,7 @@ -Review the migration log for each migrated repository. For more information, see "[AUTOTITLE](/migrations/using-github-enterprise-importer/completing-your-migration-with-github-enterprise-importer/accessing-your-migration-logs-for-github-enterprise-importer)." +Review the migration log for each migrated repository. For more information, see [AUTOTITLE](/migrations/using-github-enterprise-importer/completing-your-migration-with-github-enterprise-importer/accessing-your-migration-logs-for-github-enterprise-importer). If the migration failed, the log may contain additional information about the cause of the failure. If the migration succeeded, there may be warnings in the migration log representing specific pieces of data (for example pull requests, issues, or comments) which were not migrated or were migrated with caveats. -For more information on understanding migration warnings, see "[AUTOTITLE](/migrations/using-github-enterprise-importer/completing-your-migration-with-github-enterprise-importer/troubleshooting-your-migration-with-github-enterprise-importer#understanding-migration-log-warnings)." After reviewing any migration warnings, you will need to make a decision about whether you can accept those warnings and move forward. +For more information on understanding migration warnings, see [AUTOTITLE](/migrations/using-github-enterprise-importer/completing-your-migration-with-github-enterprise-importer/troubleshooting-your-migration-with-github-enterprise-importer#understanding-migration-log-warnings). After reviewing any migration warnings, you will need to make a decision about whether you can accept those warnings and move forward. diff --git a/data/reusables/enterprise-migration-tool/setting-repository-visibility.md b/data/reusables/enterprise-migration-tool/setting-repository-visibility.md index 7ed3f46c15c5..cf1493b2c1c9 100644 --- a/data/reusables/enterprise-migration-tool/setting-repository-visibility.md +++ b/data/reusables/enterprise-migration-tool/setting-repository-visibility.md @@ -1,5 +1,5 @@ All repositories are migrated as private by default, and only the user that ran the migration and organization owners will have access to the repository. If you don't want the repository to be private, change the visibility. * You can set a repository's visibility with the `--target-repo-visibility` CLI option or the `targetRepoVisibility` GraphQL property. -* You can change a repository's visibility in the browser. For more information, see "[AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility)." +* You can change a repository's visibility in the browser. For more information, see [AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility). * Alternatively, you can use {% data variables.product.prodname_cli %} to change repository visibility from the command line. You can even add this command to the script that was generated to run your migrations. For more information, see [`gh repo edit`](https://cli.github.com/manual/gh_repo_edit) in the {% data variables.product.prodname_cli %} documentation. diff --git a/data/reusables/enterprise-migration-tool/validate-migration-logs.md b/data/reusables/enterprise-migration-tool/validate-migration-logs.md index cd4451470e65..b4b2a9351289 100644 --- a/data/reusables/enterprise-migration-tool/validate-migration-logs.md +++ b/data/reusables/enterprise-migration-tool/validate-migration-logs.md @@ -1,3 +1,3 @@ -When your migration is complete, we recommend reviewing your migration log. For more information, see "[AUTOTITLE](/migrations/using-github-enterprise-importer/completing-your-migration-with-github-enterprise-importer/accessing-your-migration-logs-for-github-enterprise-importer)." +When your migration is complete, we recommend reviewing your migration log. For more information, see [AUTOTITLE](/migrations/using-github-enterprise-importer/completing-your-migration-with-github-enterprise-importer/accessing-your-migration-logs-for-github-enterprise-importer). We recommend that you review your migrated repositories for a soundness check. diff --git a/data/reusables/enterprise/about-deployment-methods.md b/data/reusables/enterprise/about-deployment-methods.md index a239d704c5ce..faba9b9a506e 100644 --- a/data/reusables/enterprise/about-deployment-methods.md +++ b/data/reusables/enterprise/about-deployment-methods.md @@ -1 +1 @@ -{% data variables.product.prodname_enterprise %} offers two deployment options. {% ifversion fpt or ghec %}In addition to {% data variables.product.prodname_ghe_cloud %}, you can use {% data variables.product.prodname_ghe_server %} to host development work for your enterprise in your data center or a supported cloud.{% elsif ghes %}In addition to {% data variables.product.product_name %}, you can use {% data variables.product.prodname_ghe_cloud %} to host development work for your enterprise on {% data variables.product.prodname_dotcom_the_website %}.{% endif %} For more information, see "[AUTOTITLE](/get-started/learning-about-github/githubs-plans#github-enterprise)." +{% data variables.product.prodname_enterprise %} offers two deployment options. {% ifversion fpt or ghec %}In addition to {% data variables.product.prodname_ghe_cloud %}, you can use {% data variables.product.prodname_ghe_server %} to host development work for your enterprise in your data center or a supported cloud.{% elsif ghes %}In addition to {% data variables.product.product_name %}, you can use {% data variables.product.prodname_ghe_cloud %} to host development work for your enterprise on {% data variables.product.prodname_dotcom_the_website %}.{% endif %} For more information, see [AUTOTITLE](/get-started/learning-about-github/githubs-plans#github-enterprise). diff --git a/data/reusables/enterprise/about-ssh-ports.md b/data/reusables/enterprise/about-ssh-ports.md index e8993b7d9a5d..4ff39a4641d8 100644 --- a/data/reusables/enterprise/about-ssh-ports.md +++ b/data/reusables/enterprise/about-ssh-ports.md @@ -1,5 +1,5 @@ Each {% data variables.product.product_name %} instance accepts SSH connections over two ports. Site administrators can access the administrative shell via SSH, then run command-line utilities, troubleshoot, and perform maintenance. Users can connect via SSH to access and write Git data in the instance's repositories. Users do not have shell access to your instance. For more information, see the following articles. -* "[AUTOTITLE](/admin/configuration/configuring-network-settings/network-ports)" -* "[AUTOTITLE](/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh)" -* "[AUTOTITLE](/authentication/connecting-to-github-with-ssh/about-ssh)" +* [AUTOTITLE](/admin/configuration/configuring-network-settings/network-ports) +* [AUTOTITLE](/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh) +* [AUTOTITLE](/authentication/connecting-to-github-with-ssh/about-ssh) diff --git a/data/reusables/enterprise/about-upgrades.md b/data/reusables/enterprise/about-upgrades.md index e90241c08622..9fe19dc32eb8 100644 --- a/data/reusables/enterprise/about-upgrades.md +++ b/data/reusables/enterprise/about-upgrades.md @@ -1,3 +1,3 @@ -{% data reusables.enterprise.constantly-improving %} You are responsible for upgrades to your instance. For more information, see "[AUTOTITLE](/admin/overview/about-upgrades-to-new-releases)." +{% data reusables.enterprise.constantly-improving %} You are responsible for upgrades to your instance. For more information, see [AUTOTITLE](/admin/overview/about-upgrades-to-new-releases). To upgrade an instance, you must plan and communicate the upgrade, choose the appropriate package, back up your data, and then perform the upgrade. diff --git a/data/reusables/enterprise/best-practices.md b/data/reusables/enterprise/best-practices.md index ca49baaa6efc..5f1920ada960 100644 --- a/data/reusables/enterprise/best-practices.md +++ b/data/reusables/enterprise/best-practices.md @@ -1 +1 @@ -To learn how your enterprise can use {% data variables.product.product_name %} most effectively, see "[AUTOTITLE](/admin/overview/best-practices-for-enterprises)." +To learn how your enterprise can use {% data variables.product.product_name %} most effectively, see [AUTOTITLE](/admin/overview/best-practices-for-enterprises). diff --git a/data/reusables/enterprise/editor-role-note.md b/data/reusables/enterprise/editor-role-note.md index fd0638b9d32f..51bcc41fd2d2 100644 --- a/data/reusables/enterprise/editor-role-note.md +++ b/data/reusables/enterprise/editor-role-note.md @@ -4,6 +4,6 @@ {%- ifversion ghes = 3.11 %} 3.11.8{%- endif %} {%- ifversion ghes = 3.10 %} 3.10.10{%- endif %} . For more information, see -{%- ifversion ghes = 3.12 %} "[AUTOTITLE](/enterprise-server@3.12/admin/release-notes#3.12.2-security-fixes)."{%- endif %} -{%- ifversion ghes = 3.11 %} "[AUTOTITLE](/enterprise-server@3.11/admin/release-notes#3.11.8-security-fixes)."{%- endif %} -{%- ifversion ghes = 3.10 %} "[AUTOTITLE](/enterprise-server@3.10/admin/release-notes#3.10.10-security-fixes)."{%- endif %} +{%- ifversion ghes = 3.12 %} [AUTOTITLE](/enterprise-server@3.12/admin/release-notes#3.12.2-security-fixes).{%- endif %} +{%- ifversion ghes = 3.11 %} [AUTOTITLE](/enterprise-server@3.11/admin/release-notes#3.11.8-security-fixes).{%- endif %} +{%- ifversion ghes = 3.10 %} [AUTOTITLE](/enterprise-server@3.10/admin/release-notes#3.10.10-security-fixes).{%- endif %} diff --git a/data/reusables/enterprise/link-to-ghec-trial.md b/data/reusables/enterprise/link-to-ghec-trial.md index 77c1531df76e..1508b1d548de 100644 --- a/data/reusables/enterprise/link-to-ghec-trial.md +++ b/data/reusables/enterprise/link-to-ghec-trial.md @@ -1 +1 @@ -For more information about how you can try {% data variables.product.prodname_ghe_cloud %} for free, see "[Setting up a trial of {% data variables.product.prodname_ghe_cloud %}](/admin/overview/setting-up-a-trial-of-github-enterprise-cloud)." +For more information about how you can try {% data variables.product.prodname_ghe_cloud %} for free, see [Setting up a trial of {% data variables.product.prodname_ghe_cloud %}](/admin/overview/setting-up-a-trial-of-github-enterprise-cloud). diff --git a/data/reusables/enterprise/repo-policy-rules-alternative.md b/data/reusables/enterprise/repo-policy-rules-alternative.md index 2b91002f264a..09321b2ee78a 100644 --- a/data/reusables/enterprise/repo-policy-rules-alternative.md +++ b/data/reusables/enterprise/repo-policy-rules-alternative.md @@ -1,3 +1,3 @@ {% ifversion repo-policy-rules %} -We recommend creating a **repository policy** to govern the lifecycle of repositories in your enterprise, such as who can create or delete repositories. Repository policies give you flexibility over which users are affected and which organizations and repositories are targeted. See "[AUTOTITLE](/admin/managing-accounts-and-repositories/managing-repositories-in-your-enterprise/governing-how-people-use-repositories-in-your-enterprise)." +We recommend creating a **repository policy** to govern the lifecycle of repositories in your enterprise, such as who can create or delete repositories. Repository policies give you flexibility over which users are affected and which organizations and repositories are targeted. See [AUTOTITLE](/admin/managing-accounts-and-repositories/managing-repositories-in-your-enterprise/governing-how-people-use-repositories-in-your-enterprise). {% endif %} diff --git a/data/reusables/enterprise/repo-policy-rules-more-flexible.md b/data/reusables/enterprise/repo-policy-rules-more-flexible.md index b9bead1884ce..e336b73675a5 100644 --- a/data/reusables/enterprise/repo-policy-rules-more-flexible.md +++ b/data/reusables/enterprise/repo-policy-rules-more-flexible.md @@ -1 +1 @@ -You can create a repository policy to govern who can create repositories in your organization, how new repositories must be named, and which visibilities are available. Compared to "member privilege" policies, repository policies give you more flexibility over which users are affected and which repositories are targeted. See "[AUTOTITLE](/organizations/managing-organization-settings/governing-how-people-use-repositories-in-your-organization)." +You can create a repository policy to govern who can create repositories in your organization, how new repositories must be named, and which visibilities are available. Compared to "member privilege" policies, repository policies give you more flexibility over which users are affected and which repositories are targeted. See [AUTOTITLE](/organizations/managing-organization-settings/governing-how-people-use-repositories-in-your-organization). diff --git a/data/reusables/enterprise/repo-policy-rules-with-custom-properties.md b/data/reusables/enterprise/repo-policy-rules-with-custom-properties.md index 56354d8bd5d7..49f4efcf9b33 100644 --- a/data/reusables/enterprise/repo-policy-rules-with-custom-properties.md +++ b/data/reusables/enterprise/repo-policy-rules-with-custom-properties.md @@ -2,4 +2,4 @@ We recommend using repository policies alongside **custom repository properties* For example, you can add a property to mark repositories that contain production data or other sensitive information, then prevent anyone from making those repositories public. -To create and set custom properties, see "[AUTOTITLE](/organizations/managing-organization-settings/managing-custom-properties-for-repositories-in-your-organization)." +To create and set custom properties, see [AUTOTITLE](/organizations/managing-organization-settings/managing-custom-properties-for-repositories-in-your-organization). diff --git a/data/reusables/enterprise/role-permission-hierarchy.md b/data/reusables/enterprise/role-permission-hierarchy.md index 7d03d2a82fe5..004671b4fbda 100644 --- a/data/reusables/enterprise/role-permission-hierarchy.md +++ b/data/reusables/enterprise/role-permission-hierarchy.md @@ -1,2 +1,2 @@ > [!NOTE] -> This policy only impacts repository administrators, specifically. Organization owners and security managers can always enable security features, regardless of how you set this policy. For more information, see "[AUTOTITLE](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)." +> This policy only impacts repository administrators, specifically. Organization owners and security managers can always enable security features, regardless of how you set this policy. For more information, see [AUTOTITLE](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization). diff --git a/data/reusables/enterprise/single-organizations-enterprise-migration.md b/data/reusables/enterprise/single-organizations-enterprise-migration.md index d74e8832e861..eaaa6e0d2291 100644 --- a/data/reusables/enterprise/single-organizations-enterprise-migration.md +++ b/data/reusables/enterprise/single-organizations-enterprise-migration.md @@ -1 +1 @@ -> [!NOTE] Currently, {% data variables.product.prodname_ghe_cloud %} customers who use a single organization are being automatically upgraded to an enterprise account at no additional cost. For details, see "[AUTOTITLE](/admin/managing-your-enterprise-account/creating-an-enterprise-account#what-will-happen-after-i-upgrade-my-organization)." +> [!NOTE] Currently, {% data variables.product.prodname_ghe_cloud %} customers who use a single organization are being automatically upgraded to an enterprise account at no additional cost. For details, see [AUTOTITLE](/admin/managing-your-enterprise-account/creating-an-enterprise-account#what-will-happen-after-i-upgrade-my-organization). diff --git a/data/reusables/enterprise/test-in-staging.md b/data/reusables/enterprise/test-in-staging.md index f111ad4f6b4b..0b9f2e768951 100644 --- a/data/reusables/enterprise/test-in-staging.md +++ b/data/reusables/enterprise/test-in-staging.md @@ -1 +1 @@ -{% data variables.product.company_short %} strongly recommends that you verify any new configuration for authentication in a staging environment. An incorrect configuration could result in downtime for {% data variables.location.product_location %}. For more information, see "[AUTOTITLE](/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance)." +{% data variables.product.company_short %} strongly recommends that you verify any new configuration for authentication in a staging environment. An incorrect configuration could result in downtime for {% data variables.location.product_location %}. For more information, see [AUTOTITLE](/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance). diff --git a/data/reusables/enterprise/user-messages-markdown.md b/data/reusables/enterprise/user-messages-markdown.md index 112ed51a76fe..daab06d8c57d 100644 --- a/data/reusables/enterprise/user-messages-markdown.md +++ b/data/reusables/enterprise/user-messages-markdown.md @@ -1 +1 @@ -You can use Markdown to format your message. For more information, see "[AUTOTITLE](/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/about-writing-and-formatting-on-github)." +You can use Markdown to format your message. For more information, see [AUTOTITLE](/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/about-writing-and-formatting-on-github). diff --git a/data/reusables/enterprise_clustering/cluster-ip-note.md b/data/reusables/enterprise_clustering/cluster-ip-note.md index bd88734d5371..606832d63ec2 100644 --- a/data/reusables/enterprise_clustering/cluster-ip-note.md +++ b/data/reusables/enterprise_clustering/cluster-ip-note.md @@ -4,9 +4,9 @@ {%- ifversion ghes = 3.11 %} 3.11.8{%- endif %} {%- ifversion ghes = 3.10 %} 3.10.10{%- endif %} . For more information, see -{%- ifversion ghes = 3.12 %} "[AUTOTITLE](/enterprise-server@3.12/admin/release-notes#3.12.2-security-fixes)."{%- endif %} -{%- ifversion ghes = 3.11 %} "[AUTOTITLE](/enterprise-server@3.11/admin/release-notes#3.11.8-security-fixes)."{%- endif %} -{%- ifversion ghes = 3.10 %} "[AUTOTITLE](/enterprise-server@3.10/admin/release-notes#3.10.10-security-fixes)."{%- endif %} +{%- ifversion ghes = 3.12 %} [AUTOTITLE](/enterprise-server@3.12/admin/release-notes#3.12.2-security-fixes).{%- endif %} +{%- ifversion ghes = 3.11 %} [AUTOTITLE](/enterprise-server@3.11/admin/release-notes#3.11.8-security-fixes).{%- endif %} +{%- ifversion ghes = 3.10 %} [AUTOTITLE](/enterprise-server@3.10/admin/release-notes#3.10.10-security-fixes).{%- endif %} > > {% data reusables.enterprise_clustering.failover-blocks-ips %} diff --git a/data/reusables/enterprise_clustering/health_checks.md b/data/reusables/enterprise_clustering/health_checks.md index 5920495f12fb..0527db54c4d6 100644 --- a/data/reusables/enterprise_clustering/health_checks.md +++ b/data/reusables/enterprise_clustering/health_checks.md @@ -2,4 +2,4 @@ Configure the load balancer to check the following URL. `http(s)://HOSTNAME/status` -The endpoint will return status code `200` (OK) if the node is healthy and available to service end-user requests. For more information, see "[AUTOTITLE](/admin/enterprise-management/configuring-high-availability/monitoring-a-high-availability-configuration#monitoring-replication-from-a-remote-system)." +The endpoint will return status code `200` (OK) if the node is healthy and available to service end-user requests. For more information, see [AUTOTITLE](/admin/enterprise-management/configuring-high-availability/monitoring-a-high-availability-configuration#monitoring-replication-from-a-remote-system). diff --git a/data/reusables/enterprise_clustering/load_balancer_dns.md b/data/reusables/enterprise_clustering/load_balancer_dns.md index 34595deac75b..9d4d0eb211cc 100644 --- a/data/reusables/enterprise_clustering/load_balancer_dns.md +++ b/data/reusables/enterprise_clustering/load_balancer_dns.md @@ -1 +1 @@ -DNS lookups for the {% data variables.product.prodname_ghe_server %} hostname should resolve to the load balancer. We recommend that you enable subdomain isolation. If subdomain isolation is enabled, an additional wildcard record (`*.HOSTNAME`) should also resolve to the load balancer. For more information, see "[AUTOTITLE](/admin/configuration/configuring-network-settings/enabling-subdomain-isolation)." +DNS lookups for the {% data variables.product.prodname_ghe_server %} hostname should resolve to the load balancer. We recommend that you enable subdomain isolation. If subdomain isolation is enabled, an additional wildcard record (`*.HOSTNAME`) should also resolve to the load balancer. For more information, see [AUTOTITLE](/admin/configuration/configuring-network-settings/enabling-subdomain-isolation). diff --git a/data/reusables/enterprise_clustering/replacing-a-cluster-node-modify-cluster-conf.md b/data/reusables/enterprise_clustering/replacing-a-cluster-node-modify-cluster-conf.md index 806974a25297..372c3d34c383 100644 --- a/data/reusables/enterprise_clustering/replacing-a-cluster-node-modify-cluster-conf.md +++ b/data/reusables/enterprise_clustering/replacing-a-cluster-node-modify-cluster-conf.md @@ -16,4 +16,4 @@ storage-server = true - You can choose to defer database seeding of a new MySQL replica node, resulting in being able to open your appliance to traffic sooner. For more information, see "[AUTOTITLE](/admin/monitoring-and-managing-your-instance/configuring-clustering/deferring-database-seeding)." + You can choose to defer database seeding of a new MySQL replica node, resulting in being able to open your appliance to traffic sooner. For more information, see [AUTOTITLE](/admin/monitoring-and-managing-your-instance/configuring-clustering/deferring-database-seeding). diff --git a/data/reusables/enterprise_clustering/replacing-a-cluster-node-need-three-nodes.md b/data/reusables/enterprise_clustering/replacing-a-cluster-node-need-three-nodes.md index 46dec358b4c3..010905ff71be 100644 --- a/data/reusables/enterprise_clustering/replacing-a-cluster-node-need-three-nodes.md +++ b/data/reusables/enterprise_clustering/replacing-a-cluster-node-need-three-nodes.md @@ -1 +1 @@ -1. If you're taking a node offline that provides data services, such as `git-server`, `pages-server`, or `storage-server`, evacuate the node. For more information, see "[AUTOTITLE](/admin/enterprise-management/configuring-clustering/evacuating-a-cluster-node-running-data-services)." +1. If you're taking a node offline that provides data services, such as `git-server`, `pages-server`, or `storage-server`, evacuate the node. For more information, see [AUTOTITLE](/admin/enterprise-management/configuring-clustering/evacuating-a-cluster-node-running-data-services). diff --git a/data/reusables/enterprise_clustering/replacing-a-cluster-node-replacement-name.md b/data/reusables/enterprise_clustering/replacing-a-cluster-node-replacement-name.md index 627e9b667236..36a234f481cb 100644 --- a/data/reusables/enterprise_clustering/replacing-a-cluster-node-replacement-name.md +++ b/data/reusables/enterprise_clustering/replacing-a-cluster-node-replacement-name.md @@ -1,7 +1,7 @@ 1. If you're replacing the primary Redis node, in `cluster.conf`, modify the `redis-master` value with the replacement node name. > [!NOTE] - > If your primary Redis node is also your primary MySQL node, see "[Replacing the primary MySQL node](#replacing-the-primary-mysql-node)." + > If your primary Redis node is also your primary MySQL node, see [Replacing the primary MySQL node](#replacing-the-primary-mysql-node). For example, this modified `cluster.conf` file specifies a newly provisioned cluster node, `ghe-replacement-data-node-1` as the primary Redis node: diff --git a/data/reusables/enterprise_clustering/ssh-to-a-node.md b/data/reusables/enterprise_clustering/ssh-to-a-node.md index 8ea69f566d03..b0fdff474480 100644 --- a/data/reusables/enterprise_clustering/ssh-to-a-node.md +++ b/data/reusables/enterprise_clustering/ssh-to-a-node.md @@ -1 +1 @@ -1. SSH into any node in your cluster. For more information, see "[AUTOTITLE](/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh)." +1. SSH into any node in your cluster. For more information, see [AUTOTITLE](/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh). diff --git a/data/reusables/enterprise_enterprise_support/use_ghe_cluster_support_bundle.md b/data/reusables/enterprise_enterprise_support/use_ghe_cluster_support_bundle.md index 80595569b966..ab5f4061750f 100644 --- a/data/reusables/enterprise_enterprise_support/use_ghe_cluster_support_bundle.md +++ b/data/reusables/enterprise_enterprise_support/use_ghe_cluster_support_bundle.md @@ -1,2 +1,2 @@ > [!NOTE] -> If {% data variables.location.product_location %} is in a geo-replication configuration, or if your instance is a cluster, you should use the `ghe-cluster-support-bundle` command to retrieve the support bundle. For more information, see "[AUTOTITLE](/admin/configuration/configuring-your-enterprise/command-line-utilities#ghe-cluster-support-bundle)." +> If {% data variables.location.product_location %} is in a geo-replication configuration, or if your instance is a cluster, you should use the `ghe-cluster-support-bundle` command to retrieve the support bundle. For more information, see [AUTOTITLE](/admin/configuration/configuring-your-enterprise/command-line-utilities#ghe-cluster-support-bundle). diff --git a/data/reusables/enterprise_installation/about-adjusting-resources.md b/data/reusables/enterprise_installation/about-adjusting-resources.md index 8a9ec0b5dffc..c1be4b2ee308 100644 --- a/data/reusables/enterprise_installation/about-adjusting-resources.md +++ b/data/reusables/enterprise_installation/about-adjusting-resources.md @@ -1 +1 @@ -For more information about adjusting resources for an existing instance, see "[AUTOTITLE](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-storage-capacity)" and "[AUTOTITLE](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-cpu-or-memory-resources)." +For more information about adjusting resources for an existing instance, see [AUTOTITLE](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-storage-capacity) and [AUTOTITLE](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-cpu-or-memory-resources). diff --git a/data/reusables/enterprise_installation/azure-instance-recommendation.md b/data/reusables/enterprise_installation/azure-instance-recommendation.md index 807cf2fe370e..57059647e30a 100644 --- a/data/reusables/enterprise_installation/azure-instance-recommendation.md +++ b/data/reusables/enterprise_installation/azure-instance-recommendation.md @@ -1,5 +1,5 @@ -The {% data variables.product.prodname_ghe_server %} appliance requires a premium storage data disk, and is supported on any Azure VM that supports premium storage. Azure VM types with the `s` suffix support premium storage. For more information, see "[What disk types are available in Azure?](https://docs.microsoft.com/en-us/azure/virtual-machines/disks-types#premium-ssd)" and "[Azure premium storage: design for high performance](https://docs.microsoft.com/en-us/azure/virtual-machines/premium-storage-performance)" in the Azure documentation. +The {% data variables.product.prodname_ghe_server %} appliance requires a premium storage data disk, and is supported on any Azure VM that supports premium storage. Azure VM types with the `s` suffix support premium storage. For more information, see [What disk types are available in Azure?](https://docs.microsoft.com/en-us/azure/virtual-machines/disks-types#premium-ssd) and [Azure premium storage: design for high performance](https://docs.microsoft.com/en-us/azure/virtual-machines/premium-storage-performance) in the Azure documentation. -{% data variables.product.company_short %} recommends a memory-optimized VM for {% data variables.product.prodname_ghe_server %}. For more information, see "[Memory optimized virtual machine sizes](https://docs.microsoft.com/en-us/azure/virtual-machines/sizes-memory)" in the Azure documentation. +{% data variables.product.company_short %} recommends a memory-optimized VM for {% data variables.product.prodname_ghe_server %}. For more information, see [Memory optimized virtual machine sizes](https://docs.microsoft.com/en-us/azure/virtual-machines/sizes-memory) in the Azure documentation. -{% data variables.product.prodname_ghe_server %} supports any region that supports your VM type. For more information about the supported regions for each VM, see Azure's "[Products available by region](https://azure.microsoft.com/regions/services/)." +{% data variables.product.prodname_ghe_server %} supports any region that supports your VM type. For more information about the supported regions for each VM, see Azure's [Products available by region](https://azure.microsoft.com/regions/services/). diff --git a/data/reusables/enterprise_installation/create-ghe-instance.md b/data/reusables/enterprise_installation/create-ghe-instance.md index 9209dc7f5382..d4b8194ff61a 100644 --- a/data/reusables/enterprise_installation/create-ghe-instance.md +++ b/data/reusables/enterprise_installation/create-ghe-instance.md @@ -1 +1 @@ -To create the instance, you'll need to import the {% data variables.product.prodname_ghe_server %} image to your virtual machine and attach an additional storage volume for your instance data. For more information, see "[Hardware considerations](#hardware-considerations)." +To create the instance, you'll need to import the {% data variables.product.prodname_ghe_server %} image to your virtual machine and attach an additional storage volume for your instance data. For more information, see [Hardware considerations](#hardware-considerations). diff --git a/data/reusables/enterprise_installation/disable-github-pages-warning.md b/data/reusables/enterprise_installation/disable-github-pages-warning.md index 9f7aa8f7dae5..4b46243af6bd 100644 --- a/data/reusables/enterprise_installation/disable-github-pages-warning.md +++ b/data/reusables/enterprise_installation/disable-github-pages-warning.md @@ -1,6 +1,6 @@ {% ifversion ghes %} > [!WARNING] -> If subdomain isolation is disabled, we recommend also disabling {% data variables.product.prodname_pages %} on your enterprise. There will be no way to isolate user-supplied {% data variables.product.prodname_pages %} content from the rest of your enterprise's data. For more information, see "[AUTOTITLE](/admin/configuration/configuring-your-enterprise/configuring-github-pages-for-your-enterprise)." +> If subdomain isolation is disabled, we recommend also disabling {% data variables.product.prodname_pages %} on your enterprise. There will be no way to isolate user-supplied {% data variables.product.prodname_pages %} content from the rest of your enterprise's data. For more information, see [AUTOTITLE](/admin/configuration/configuring-your-enterprise/configuring-github-pages-for-your-enterprise). {% endif %} diff --git a/data/reusables/enterprise_installation/download-license.md b/data/reusables/enterprise_installation/download-license.md index 545c336c615c..45a7e29fda3d 100644 --- a/data/reusables/enterprise_installation/download-license.md +++ b/data/reusables/enterprise_installation/download-license.md @@ -1 +1 @@ -1. Download your license. For more information, see "[AUTOTITLE](/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise)." +1. Download your license. For more information, see [AUTOTITLE](/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise). diff --git a/data/reusables/enterprise_installation/download-note.md b/data/reusables/enterprise_installation/download-note.md index 6e995939bad1..61b62f94cdc5 100644 --- a/data/reusables/enterprise_installation/download-note.md +++ b/data/reusables/enterprise_installation/download-note.md @@ -1 +1 @@ -> [!NOTE] If you've enabled automatic update checks, you don't need to download the upgrade package and can use the file that was automatically downloaded. For more information, see "[AUTOTITLE](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/enabling-automatic-update-checks)." +> [!NOTE] If you've enabled automatic update checks, you don't need to download the upgrade package and can use the file that was automatically downloaded. For more information, see [AUTOTITLE](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/enabling-automatic-update-checks). diff --git a/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md b/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md index 8bc40fbdc9e2..228485cc4c86 100644 --- a/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md +++ b/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md @@ -10,7 +10,7 @@ We recommend different hardware configurations depending on the number of user l {% data reusables.actions.more-resources-for-ghes %} -If you plan to enable {% data variables.product.prodname_container_registry %} for the users of your instance, more resources are required. For more information about these requirements, see "[AUTOTITLE](/admin/packages/getting-started-with-github-packages-for-your-enterprise)." +If you plan to enable {% data variables.product.prodname_container_registry %} for the users of your instance, more resources are required. For more information about these requirements, see [AUTOTITLE](/admin/packages/getting-started-with-github-packages-for-your-enterprise). {% data reusables.enterprise_installation.about-adjusting-resources %} @@ -18,18 +18,18 @@ If you plan to enable {% data variables.product.prodname_container_registry %} f We recommend a high-performance SSD with high input/output operations per second (IOPS) and low latency for {% data variables.product.prodname_ghe_server %}. Workloads are I/O intensive. If you use a bare metal hypervisor, we recommend directly attaching the disk or using a disk from a storage area network (SAN). -Your instance requires a persistent data disk separate from the root disk. For more information, see "[AUTOTITLE](/admin/overview/system-overview)." +Your instance requires a persistent data disk separate from the root disk. For more information, see [AUTOTITLE](/admin/overview/system-overview). >[!WARNING] ->Root storage refers to the total size of your instance's root disk. When the instance is booted you will see {% ifversion ghes > 3.14 %}200GB available on the root filesystem. The remaining 200GB{% else %}100GB available on the root filesystem. The remaining 100GB{% endif %} is reserved for upgrades. For more information, see "[AUTOTITLE](/admin/overview/system-overview#storage-architecture)." +>Root storage refers to the total size of your instance's root disk. When the instance is booted you will see {% ifversion ghes > 3.14 %}200GB available on the root filesystem. The remaining 200GB{% else %}100GB available on the root filesystem. The remaining 100GB{% endif %} is reserved for upgrades. For more information, see [AUTOTITLE](/admin/overview/system-overview#storage-architecture). {% ifversion ghes %} -To configure {% data variables.product.prodname_actions %}, you must provide external blob storage. 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##external-storage-requirements)." +To configure {% data variables.product.prodname_actions %}, you must provide external blob storage. 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##external-storage-requirements). {% endif %} -The available space on the root filesystem will be 50% of the total disk size. You can resize your instance's root disk by building a new instance or using an existing instance. For more information, see "[AUTOTITLE](/admin/overview/system-overview#storage-architecture)" and "[AUTOTITLE](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-storage-capacity)." +The available space on the root filesystem will be 50% of the total disk size. You can resize your instance's root disk by building a new instance or using an existing instance. For more information, see [AUTOTITLE](/admin/overview/system-overview#storage-architecture) and [AUTOTITLE](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-storage-capacity). ### CPU and memory @@ -39,15 +39,15 @@ Any VMs you provision for {% data variables.location.product_location %} must us {% ifversion ghes %} -If you plan to enable {% data variables.product.prodname_actions %} for the users of your {% data variables.product.prodname_ghe_server %} instance, you may need to provision additional CPU and memory resources 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#review-hardware-considerations)." +If you plan to enable {% data variables.product.prodname_actions %} for the users of your {% data variables.product.prodname_ghe_server %} instance, you may need to provision additional CPU and memory resources 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#review-hardware-considerations). {% endif %} {% data reusables.enterprise_installation.increasing-cpus-req %} > [!WARNING] -> We recommend that users configure webhook events to notify external systems of activity on {% data variables.product.prodname_ghe_server %}. Automated checks for changes, or _polling_, will negatively impact the performance and scalability of your instance. For more information, see "[AUTOTITLE](/get-started/exploring-integrations/about-webhooks)." +> We recommend that users configure webhook events to notify external systems of activity on {% data variables.product.prodname_ghe_server %}. Automated checks for changes, or _polling_, will negatively impact the performance and scalability of your instance. For more information, see [AUTOTITLE](/get-started/exploring-integrations/about-webhooks). -For more information about monitoring the capacity and performance of {% data variables.product.prodname_ghe_server %}, see "[AUTOTITLE](/admin/enterprise-management/monitoring-your-appliance)." +For more information about monitoring the capacity and performance of {% data variables.product.prodname_ghe_server %}, see [AUTOTITLE](/admin/enterprise-management/monitoring-your-appliance). -You can increase your instance's CPU or memory resources. For more information, see "[AUTOTITLE](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-cpu-or-memory-resources)." +You can increase your instance's CPU or memory resources. For more information, see [AUTOTITLE](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-cpu-or-memory-resources). diff --git a/data/reusables/enterprise_installation/hotpatching-explanation.md b/data/reusables/enterprise_installation/hotpatching-explanation.md index 9eff688e9880..5a27285fac30 100644 --- a/data/reusables/enterprise_installation/hotpatching-explanation.md +++ b/data/reusables/enterprise_installation/hotpatching-explanation.md @@ -4,4 +4,4 @@ You can use hotpatching to upgrade to a newer patch release, but not a feature r Hotpatches do not always require a reboot. When you install the hotpatch, you'll see a message in the terminal if any of the packages need a reboot to complete the update. You can schedule this reboot at a convenient time but we recommend rebooting as soon as practical, especially if there are any security fixes. -Hotpatches require a configuration run, which can cause a brief period of errors or unresponsiveness for some or all services on {% data variables.location.product_location %}. You are not required to enable maintenance mode during installation of a hotpatch, but doing so will guarantee that users see a maintenance page instead of errors or timeouts. See "[AUTOTITLE](/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode)." +Hotpatches require a configuration run, which can cause a brief period of errors or unresponsiveness for some or all services on {% data variables.location.product_location %}. You are not required to enable maintenance mode during installation of a hotpatch, but doing so will guarantee that users see a maintenance page instead of errors or timeouts. See [AUTOTITLE](/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode). diff --git a/data/reusables/enterprise_installation/increase-resources-communicate-and-enable-maintenance-mode.md b/data/reusables/enterprise_installation/increase-resources-communicate-and-enable-maintenance-mode.md index c1e90c69de10..91620db2a2e1 100644 --- a/data/reusables/enterprise_installation/increase-resources-communicate-and-enable-maintenance-mode.md +++ b/data/reusables/enterprise_installation/increase-resources-communicate-and-enable-maintenance-mode.md @@ -1,4 +1,4 @@ 1. Communicate the upcoming downtime to your users and enable maintenance mode. For more information, see the following articles. - * "[AUTOTITLE](/admin/managing-accounts-and-repositories/communicating-information-to-users-in-your-enterprise/customizing-user-messages-for-your-enterprise#creating-a-mandatory-message)" - * "[AUTOTITLE](/admin/administering-your-instance/configuring-maintenance-mode/enabling-and-scheduling-maintenance-mode)" + * [AUTOTITLE](/admin/managing-accounts-and-repositories/communicating-information-to-users-in-your-enterprise/customizing-user-messages-for-your-enterprise#creating-a-mandatory-message) + * [AUTOTITLE](/admin/administering-your-instance/configuring-maintenance-mode/enabling-and-scheduling-maintenance-mode) diff --git a/data/reusables/enterprise_installation/increase-resources-shut-down.md b/data/reusables/enterprise_installation/increase-resources-shut-down.md index a84ba9dacd4c..a8a17938ea6a 100644 --- a/data/reusables/enterprise_installation/increase-resources-shut-down.md +++ b/data/reusables/enterprise_installation/increase-resources-shut-down.md @@ -1,4 +1,4 @@ -1. To stop the instance, SSH into the instance, then run the following command. For more information, see "[AUTOTITLE](/admin/administering-your-instance/administering-your-instance-from-the-command-line/accessing-the-administrative-shell-ssh)." +1. To stop the instance, SSH into the instance, then run the following command. For more information, see [AUTOTITLE](/admin/administering-your-instance/administering-your-instance-from-the-command-line/accessing-the-administrative-shell-ssh). ```shell sudo poweroff diff --git a/data/reusables/enterprise_installation/increase-resources-test-in-maintenance-mode.md b/data/reusables/enterprise_installation/increase-resources-test-in-maintenance-mode.md index f96da497ec3a..65d4295e133d 100644 --- a/data/reusables/enterprise_installation/increase-resources-test-in-maintenance-mode.md +++ b/data/reusables/enterprise_installation/increase-resources-test-in-maintenance-mode.md @@ -1,3 +1,3 @@ {%- ifversion ip-exception-list %} -1. Optionally, you can validate the changes by configuring an IP exception list to allow access from specified IP addresses. For more information, see "[AUTOTITLE](/admin/administering-your-instance/configuring-maintenance-mode/enabling-and-scheduling-maintenance-mode#validating-changes-in-maintenance-mode-using-the-ip-exception-list)." +1. Optionally, you can validate the changes by configuring an IP exception list to allow access from specified IP addresses. For more information, see [AUTOTITLE](/admin/administering-your-instance/configuring-maintenance-mode/enabling-and-scheduling-maintenance-mode#validating-changes-in-maintenance-mode-using-the-ip-exception-list). {%- endif %} diff --git a/data/reusables/enterprise_installation/replication-status-upgrade.md b/data/reusables/enterprise_installation/replication-status-upgrade.md index 9f27796ddc27..6b59b87ce3f9 100644 --- a/data/reusables/enterprise_installation/replication-status-upgrade.md +++ b/data/reusables/enterprise_installation/replication-status-upgrade.md @@ -13,4 +13,4 @@ If the command returns `Replication is not running`, the replication may still b > CRITICAL: mssql replication is down, didn't find Token_Configuration! > ``` - If `ghe-repl-status` did not return `OK`, and the explanation isn't listed in the note above, contact {% data variables.contact.enterprise_support %}. For more information, see "[AUTOTITLE](/support/contacting-github-support)." + If `ghe-repl-status` did not return `OK`, and the explanation isn't listed in the note above, contact {% data variables.contact.enterprise_support %}. For more information, see [AUTOTITLE](/support/contacting-github-support). diff --git a/data/reusables/enterprise_installation/request-a-trial.md b/data/reusables/enterprise_installation/request-a-trial.md index 4c4919b71fae..a2f0351e3b35 100644 --- a/data/reusables/enterprise_installation/request-a-trial.md +++ b/data/reusables/enterprise_installation/request-a-trial.md @@ -1 +1 @@ -You can request a trial to evaluate {% data variables.product.prodname_ghe_server %}. For more information, see "[Setting up a trial of {% data variables.product.prodname_ghe_server %}](/admin/overview/setting-up-a-trial-of-github-enterprise-server)." +You can request a trial to evaluate {% data variables.product.prodname_ghe_server %}. For more information, see [Setting up a trial of {% data variables.product.prodname_ghe_server %}](/admin/overview/setting-up-a-trial-of-github-enterprise-server). diff --git a/data/reusables/enterprise_installation/software-license.md b/data/reusables/enterprise_installation/software-license.md index 9ecbdc0faf22..a94fa9ccb96d 100644 --- a/data/reusables/enterprise_installation/software-license.md +++ b/data/reusables/enterprise_installation/software-license.md @@ -1 +1 @@ -You must have a {% data variables.product.prodname_enterprise %} license file. For more information, see "[AUTOTITLE](/admin/overview/setting-up-a-trial-of-github-enterprise-server)" and "[AUTOTITLE](/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise)." +You must have a {% data variables.product.prodname_enterprise %} license file. For more information, see [AUTOTITLE](/admin/overview/setting-up-a-trial-of-github-enterprise-server) and [AUTOTITLE](/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise). diff --git a/data/reusables/enterprise_installation/ssh-into-cluster-node.md b/data/reusables/enterprise_installation/ssh-into-cluster-node.md index 22986ce026ad..5e33d39093fd 100644 --- a/data/reusables/enterprise_installation/ssh-into-cluster-node.md +++ b/data/reusables/enterprise_installation/ssh-into-cluster-node.md @@ -1,4 +1,4 @@ -1. To connect to {% data variables.location.product_location %}, SSH into any of your cluster's nodes. From your workstation, run the following command. Replace HOSTNAME with the node's hostname. For more information, see "[AUTOTITLE](/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh)." +1. To connect to {% data variables.location.product_location %}, SSH into any of your cluster's nodes. From your workstation, run the following command. Replace HOSTNAME with the node's hostname. For more information, see [AUTOTITLE](/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh). ```shell copy ssh -p 122 admin@HOSTNAME diff --git a/data/reusables/enterprise_installation/ssh-into-staging-instance.md b/data/reusables/enterprise_installation/ssh-into-staging-instance.md index 8126b1c59763..935536db53ba 100644 --- a/data/reusables/enterprise_installation/ssh-into-staging-instance.md +++ b/data/reusables/enterprise_installation/ssh-into-staging-instance.md @@ -1,4 +1,4 @@ -1. SSH into the staging instance. For more information, see "[AUTOTITLE](/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh)." +1. SSH into the staging instance. For more information, see [AUTOTITLE](/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh). ```shell copy ssh -p 122 admin@HOSTNAME diff --git a/data/reusables/enterprise_installation/upload-a-license-file.md b/data/reusables/enterprise_installation/upload-a-license-file.md index 5ebfdca0a0f5..fcf6cec80b33 100644 --- a/data/reusables/enterprise_installation/upload-a-license-file.md +++ b/data/reusables/enterprise_installation/upload-a-license-file.md @@ -1 +1 @@ -1. At the prompt, upload your license file and set a management console password. For more information, see "[AUTOTITLE](/billing/managing-your-license-for-github-enterprise)." +1. At the prompt, upload your license file and set a management console password. For more information, see [AUTOTITLE](/billing/managing-your-license-for-github-enterprise). diff --git a/data/reusables/enterprise_installation/warning-on-upgrading-physical-resources.md b/data/reusables/enterprise_installation/warning-on-upgrading-physical-resources.md index 5395ec9db5e5..72c8d10af4b7 100644 --- a/data/reusables/enterprise_installation/warning-on-upgrading-physical-resources.md +++ b/data/reusables/enterprise_installation/warning-on-upgrading-physical-resources.md @@ -1 +1 @@ -The process for allocating new system resources varies by virtualization platform and resource type. You should always configure the monitoring and alerting of key system resources. For more information, see "[AUTOTITLE](/admin/enterprise-management/monitoring-your-appliance)." +The process for allocating new system resources varies by virtualization platform and resource type. You should always configure the monitoring and alerting of key system resources. For more information, see [AUTOTITLE](/admin/enterprise-management/monitoring-your-appliance). diff --git a/data/reusables/enterprise_installation/when-9418-necessary.md b/data/reusables/enterprise_installation/when-9418-necessary.md index 44881b401520..0db417862d1b 100644 --- a/data/reusables/enterprise_installation/when-9418-necessary.md +++ b/data/reusables/enterprise_installation/when-9418-necessary.md @@ -1 +1 @@ -If you have enabled private mode on your instance, then opening this port is only required if you also enabled anonymous Git read access. For more information, see "[AUTOTITLE](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#configuring-anonymous-git-read-access)." +If you have enabled private mode on your instance, then opening this port is only required if you also enabled anonymous Git read access. For more information, see [AUTOTITLE](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#configuring-anonymous-git-read-access). diff --git a/data/reusables/enterprise_management_console/api-deprecation.md b/data/reusables/enterprise_management_console/api-deprecation.md index e929452dcda0..74b8b6790b2b 100644 --- a/data/reusables/enterprise_management_console/api-deprecation.md +++ b/data/reusables/enterprise_management_console/api-deprecation.md @@ -1,6 +1,6 @@ {% ifversion management-console-manage-ghes-parity %} > [!NOTE] -> The {% data variables.enterprise.management_console %} endpoints will be deprecated in a future version of {% data variables.product.prodname_ghe_server %}. You can access the same functionality using the Manage {% data variables.product.prodname_ghe_server %} endpoints. For more information, see "[AUTOTITLE](/rest/enterprise-admin/manage-ghes)." +> The {% data variables.enterprise.management_console %} endpoints will be deprecated in a future version of {% data variables.product.prodname_ghe_server %}. You can access the same functionality using the Manage {% data variables.product.prodname_ghe_server %} endpoints. For more information, see [AUTOTITLE](/rest/enterprise-admin/manage-ghes). {% endif %} diff --git a/data/reusables/enterprise_management_console/test-domain-settings-failure.md b/data/reusables/enterprise_management_console/test-domain-settings-failure.md index f6e72109813e..1cde36f24e28 100644 --- a/data/reusables/enterprise_management_console/test-domain-settings-failure.md +++ b/data/reusables/enterprise_management_console/test-domain-settings-failure.md @@ -1 +1 @@ -1. If you don't receive a green checkmark next to all entries, review your configuration for the setting that failed. For more information, see "[AUTOTITLE](/admin/configuration/configuring-network-settings/configuring-dns-nameservers)." +1. If you don't receive a green checkmark next to all entries, review your configuration for the setting that failed. For more information, see [AUTOTITLE](/admin/configuration/configuring-network-settings/configuring-dns-nameservers). diff --git a/data/reusables/enterprise_management_console/type-management-console-password.md b/data/reusables/enterprise_management_console/type-management-console-password.md index 0659306b5d86..2fb3c67ac288 100644 --- a/data/reusables/enterprise_management_console/type-management-console-password.md +++ b/data/reusables/enterprise_management_console/type-management-console-password.md @@ -1,5 +1,5 @@ {%- 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. 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. diff --git a/data/reusables/enterprise_management_console/unlocking-management-console-with-shell.md b/data/reusables/enterprise_management_console/unlocking-management-console-with-shell.md index 867f3f5e416f..de72c870971d 100644 --- a/data/reusables/enterprise_management_console/unlocking-management-console-with-shell.md +++ b/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 %}{% 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). diff --git a/data/reusables/enterprise_migrations/locking-repositories.md b/data/reusables/enterprise_migrations/locking-repositories.md index ed0da5d3533e..d72d7130f3ff 100644 --- a/data/reusables/enterprise_migrations/locking-repositories.md +++ b/data/reusables/enterprise_migrations/locking-repositories.md @@ -1,4 +1,4 @@ > [!NOTE] > Locking a repository prevents all write access to the repository. You cannot associate new teams or collaborators with a locked repository. > ->If you're performing a trial run, you do not need to lock the repository. When you migrate data from a repository that's in use, {% data variables.product.company_short %} strongly recommends locking the repository. For more information, see "[AUTOTITLE](/migrations/using-ghe-migrator/about-ghe-migrator#types-of-migrations)." +>If you're performing a trial run, you do not need to lock the repository. When you migrate data from a repository that's in use, {% data variables.product.company_short %} strongly recommends locking the repository. For more information, see [AUTOTITLE](/migrations/using-ghe-migrator/about-ghe-migrator#types-of-migrations). diff --git a/data/reusables/enterprise_migrations/ready-to-import-migrations.md b/data/reusables/enterprise_migrations/ready-to-import-migrations.md index 48011f01db71..e2bf56a3af70 100644 --- a/data/reusables/enterprise_migrations/ready-to-import-migrations.md +++ b/data/reusables/enterprise_migrations/ready-to-import-migrations.md @@ -1 +1 @@ -1. To prepare the archived migration data for import into a {% data variables.product.prodname_ghe_server %} instance, see "[AUTOTITLE](/migrations/using-ghe-migrator/migrating-data-to-github-enterprise-server#preparing-the-migrated-data)". +1. To prepare the archived migration data for import into a {% data variables.product.prodname_ghe_server %} instance, see [AUTOTITLE](/migrations/using-ghe-migrator/migrating-data-to-github-enterprise-server#preparing-the-migrated-data). diff --git a/data/reusables/enterprise_site_admin_settings/add-key-to-web-flow-user.md b/data/reusables/enterprise_site_admin_settings/add-key-to-web-flow-user.md index 75794fcbc5f5..fb1edd550423 100644 --- a/data/reusables/enterprise_site_admin_settings/add-key-to-web-flow-user.md +++ b/data/reusables/enterprise_site_admin_settings/add-key-to-web-flow-user.md @@ -6,7 +6,7 @@ 1. Copy your PGP key, beginning with `-----BEGIN PGP PUBLIC KEY BLOCK-----` and ending with `-----END PGP PUBLIC KEY BLOCK-----`. 1. Sign into {% data variables.product.prodname_ghe_server %} as the user created for web commit signing, for example, `web-flow`. -1. Add the public PGP key to the user's profile. For more information, see "[AUTOTITLE](/authentication/managing-commit-signature-verification/adding-a-gpg-key-to-your-github-account)." +1. Add the public PGP key to the user's profile. For more information, see [AUTOTITLE](/authentication/managing-commit-signature-verification/adding-a-gpg-key-to-your-github-account). > [!NOTE] > Do not remove other public keys from the list of GPG keys. If a public key is deleted, any commits signed with the corresponding private key will no longer be marked as verified. diff --git a/data/reusables/enterprise_site_admin_settings/maintenance-mode-status.md b/data/reusables/enterprise_site_admin_settings/maintenance-mode-status.md index 58307e656431..1d9ee0487843 100644 --- a/data/reusables/enterprise_site_admin_settings/maintenance-mode-status.md +++ b/data/reusables/enterprise_site_admin_settings/maintenance-mode-status.md @@ -1,2 +1,2 @@ > [!NOTE] -> When the appliance is in maintenance mode, the `https://HOSTNAME/status` URL will return status code `503` (Service Unavailable). For more information, see "[AUTOTITLE](/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode)." +> When the appliance is in maintenance mode, the `https://HOSTNAME/status` URL will return status code `503` (Service Unavailable). For more information, see [AUTOTITLE](/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode). diff --git a/data/reusables/enterprise_site_admin_settings/management-console-access.md b/data/reusables/enterprise_site_admin_settings/management-console-access.md index c1650cb0c65e..c3209cdf2d3c 100644 --- a/data/reusables/enterprise_site_admin_settings/management-console-access.md +++ b/data/reusables/enterprise_site_admin_settings/management-console-access.md @@ -1,5 +1,5 @@ ## About access to the {% data variables.enterprise.management_console %} -{% 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)." +{% 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 %}. diff --git a/data/reusables/enterprise_site_admin_settings/sign-in-as-root-administrator.md b/data/reusables/enterprise_site_admin_settings/sign-in-as-root-administrator.md index 505767103e63..af2fcc5962cd 100644 --- a/data/reusables/enterprise_site_admin_settings/sign-in-as-root-administrator.md +++ b/data/reusables/enterprise_site_admin_settings/sign-in-as-root-administrator.md @@ -1 +1 @@ -1. Sign into the {% data variables.enterprise.management_console %} as the root site administrator. For more information, see "[AUTOTITLE](/admin/configuration/administering-your-instance-from-the-management-console/accessing-the-management-console)." +1. Sign into the {% data variables.enterprise.management_console %} as the root site administrator. For more information, see [AUTOTITLE](/admin/configuration/administering-your-instance-from-the-management-console/accessing-the-management-console). diff --git a/data/reusables/enterprise_user_management/SAML-to-OIDC-migration-for-EMU.md b/data/reusables/enterprise_user_management/SAML-to-OIDC-migration-for-EMU.md index f20fbad50491..bf1fdbcd77cc 100644 --- a/data/reusables/enterprise_user_management/SAML-to-OIDC-migration-for-EMU.md +++ b/data/reusables/enterprise_user_management/SAML-to-OIDC-migration-for-EMU.md @@ -1 +1 @@ -If you currently use SAML SSO for authentication and would prefer to use OIDC and benefit from CAP support, you can follow a migration path. For more information, see "[AUTOTITLE](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/migrating-from-saml-to-oidc)." +If you currently use SAML SSO for authentication and would prefer to use OIDC and benefit from CAP support, you can follow a migration path. For more information, see [AUTOTITLE](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/migrating-from-saml-to-oidc). diff --git a/data/reusables/enterprise_user_management/alternatively-enable-external-authentication.md b/data/reusables/enterprise_user_management/alternatively-enable-external-authentication.md index c02f92af602e..58ccbeade70e 100644 --- a/data/reusables/enterprise_user_management/alternatively-enable-external-authentication.md +++ b/data/reusables/enterprise_user_management/alternatively-enable-external-authentication.md @@ -1 +1 @@ -Alternatively, you can configure external authentication for {% data variables.location.product_location %}. If you use external authentication, you must invite people to use your instance through your authentication provider. For more information, see "[AUTOTITLE](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise#external-authentication)." +Alternatively, you can configure external authentication for {% data variables.location.product_location %}. If you use external authentication, you must invite people to use your instance through your authentication provider. For more information, see [AUTOTITLE](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise#external-authentication). diff --git a/data/reusables/enterprise_user_management/built-in-authentication-option.md b/data/reusables/enterprise_user_management/built-in-authentication-option.md index 8858826f1a44..c31801e77201 100644 --- a/data/reusables/enterprise_user_management/built-in-authentication-option.md +++ b/data/reusables/enterprise_user_management/built-in-authentication-option.md @@ -1 +1 @@ -Optionally, to allow people without an account on your external authentication system to sign in with built-in authentication, select **Allow built-in authentication**. For more information, see "[AUTOTITLE](/admin/identity-and-access-management/managing-iam-for-your-enterprise/allowing-built-in-authentication-for-users-outside-your-provider)." +Optionally, to allow people without an account on your external authentication system to sign in with built-in authentication, select **Allow built-in authentication**. For more information, see [AUTOTITLE](/admin/identity-and-access-management/managing-iam-for-your-enterprise/allowing-built-in-authentication-for-users-outside-your-provider). diff --git a/data/reusables/enterprise_user_management/built-in-authentication.md b/data/reusables/enterprise_user_management/built-in-authentication.md index 712d2eb1f329..81a707f84d8c 100644 --- a/data/reusables/enterprise_user_management/built-in-authentication.md +++ b/data/reusables/enterprise_user_management/built-in-authentication.md @@ -1 +1 @@ -If you want to allow authentication for some people who don't have an account on your external authentication provider, you can allow fallback authentication to local accounts on {% data variables.location.product_location %}. For more information, see "[AUTOTITLE](/admin/identity-and-access-management/managing-iam-for-your-enterprise/allowing-built-in-authentication-for-users-outside-your-provider)." +If you want to allow authentication for some people who don't have an account on your external authentication provider, you can allow fallback authentication to local accounts on {% data variables.location.product_location %}. For more information, see [AUTOTITLE](/admin/identity-and-access-management/managing-iam-for-your-enterprise/allowing-built-in-authentication-for-users-outside-your-provider). diff --git a/data/reusables/enterprise_user_management/external_auth_disables_2fa.md b/data/reusables/enterprise_user_management/external_auth_disables_2fa.md index c991cb477fca..3321688fa036 100644 --- a/data/reusables/enterprise_user_management/external_auth_disables_2fa.md +++ b/data/reusables/enterprise_user_management/external_auth_disables_2fa.md @@ -1 +1 @@ -When using SAML or CAS, two-factor authentication is not supported or managed on the {% data variables.product.prodname_ghe_server %} instance, but may be supported by the external authentication provider. Two-factor authentication enforcement on organizations is not available. For more information about enforcing two-factor authentication on organizations, see "[AUTOTITLE](/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/requiring-two-factor-authentication-in-your-organization)." +When using SAML or CAS, two-factor authentication is not supported or managed on the {% data variables.product.prodname_ghe_server %} instance, but may be supported by the external authentication provider. Two-factor authentication enforcement on organizations is not available. For more information about enforcing two-factor authentication on organizations, see [AUTOTITLE](/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/requiring-two-factor-authentication-in-your-organization). diff --git a/data/reusables/enterprise_user_management/ghec-supported-idps.md b/data/reusables/enterprise_user_management/ghec-supported-idps.md index 6a8f9586c14a..52832470c4cf 100644 --- a/data/reusables/enterprise_user_management/ghec-supported-idps.md +++ b/data/reusables/enterprise_user_management/ghec-supported-idps.md @@ -1,3 +1,3 @@ -If you choose to create an enterprise that uses personal accounts on {% data variables.product.prodname_dotcom_the_website %}, you can configure additional authentication with an external identity management system that adheres to the SAML 2.0 standard. {% data variables.product.company_short %} also officially supports and tests some identity management systems. For more information, see "[AUTOTITLE](/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise#supported-identity-providers)." +If you choose to create an enterprise that uses personal accounts on {% data variables.product.prodname_dotcom_the_website %}, you can configure additional authentication with an external identity management system that adheres to the SAML 2.0 standard. {% data variables.product.company_short %} also officially supports and tests some identity management systems. For more information, see [AUTOTITLE](/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise#supported-identity-providers). -{% data reusables.enterprise_user_management.emu-paved-path-iam-integrations %} If you use a partner identity provider (IdP), you can configure one application on your IdP to provide authentication and provisioning. The IdP must support the SAML 2.0 standard. Alternatively, if you use Entra ID (previously known as Azure AD), you can configure OpenID Connect (OIDC) authentication. If you don't use a partner IdP, or if you only use a partner IdP for authentication, you can integrate IdPs that implement the SAML 2.0 and System for Cross-domain Identity Management (SCIM) 2.0 standards. For more information, see "[AUTOTITLE](/admin/identity-and-access-management/understanding-iam-for-enterprises/about-enterprise-managed-users#about-authentication-and-user-provisioning)." +{% data reusables.enterprise_user_management.emu-paved-path-iam-integrations %} If you use a partner identity provider (IdP), you can configure one application on your IdP to provide authentication and provisioning. The IdP must support the SAML 2.0 standard. Alternatively, if you use Entra ID (previously known as Azure AD), you can configure OpenID Connect (OIDC) authentication. If you don't use a partner IdP, or if you only use a partner IdP for authentication, you can integrate IdPs that implement the SAML 2.0 and System for Cross-domain Identity Management (SCIM) 2.0 standards. For more information, see [AUTOTITLE](/admin/identity-and-access-management/understanding-iam-for-enterprises/about-enterprise-managed-users#about-authentication-and-user-provisioning). diff --git a/data/reusables/enterprise_user_management/ldap-sync-nested-teams.md b/data/reusables/enterprise_user_management/ldap-sync-nested-teams.md index 9f173b7cfd7a..51988782bc89 100644 --- a/data/reusables/enterprise_user_management/ldap-sync-nested-teams.md +++ b/data/reusables/enterprise_user_management/ldap-sync-nested-teams.md @@ -1,3 +1,3 @@ {% ifversion ghes %} -As part of its optimization configuration, LDAP Sync will not transfer your nested team structure. To create child and parent team relationships, you must manually recreate the nested team structure and sync it with the corresponding LDAP group. For more information, see "[AUTOTITLE](/organizations/organizing-members-into-teams/creating-a-team#creating-teams-with-ldap-sync-enabled)" +As part of its optimization configuration, LDAP Sync will not transfer your nested team structure. To create child and parent team relationships, you must manually recreate the nested team structure and sync it with the corresponding LDAP group. For more information, see [AUTOTITLE](/organizations/organizing-members-into-teams/creating-a-team#creating-teams-with-ldap-sync-enabled) {% endif %} diff --git a/data/reusables/enterprise_user_management/manage-global-webhooks-api.md b/data/reusables/enterprise_user_management/manage-global-webhooks-api.md index 104275e1251d..c2caab4a6f01 100644 --- a/data/reusables/enterprise_user_management/manage-global-webhooks-api.md +++ b/data/reusables/enterprise_user_management/manage-global-webhooks-api.md @@ -1,3 +1,3 @@ {% ifversion ghes %} -You can also use the REST API to manage global webhooks. For a complete list of endpoints, see "[AUTOTITLE](/rest/enterprise-admin/global-webhooks)." +You can also use the REST API to manage global webhooks. For a complete list of endpoints, see [AUTOTITLE](/rest/enterprise-admin/global-webhooks). {% endif %} diff --git a/data/reusables/enterprise_user_management/migration-teams-warning.md b/data/reusables/enterprise_user_management/migration-teams-warning.md index cacdbe21c553..614394a5388e 100644 --- a/data/reusables/enterprise_user_management/migration-teams-warning.md +++ b/data/reusables/enterprise_user_management/migration-teams-warning.md @@ -1 +1 @@ -When you migrate to a new IdP or tenant, connections between {% data variables.product.prodname_dotcom %} teams and IdP groups are removed, and are not reinstated after the migration. This will remove all members from the team and leave the team unconnected to your IdP, which may cause disruption if you use team sync to manage access to organizations or licenses from your IdP. We recommend you use the "External groups" endpoints of the REST API to gather information about your teams setup before you migrate, and to reinstate connections afterwards. For more information, see "[AUTOTITLE](/rest/teams/external-groups)." +When you migrate to a new IdP or tenant, connections between {% data variables.product.prodname_dotcom %} teams and IdP groups are removed, and are not reinstated after the migration. This will remove all members from the team and leave the team unconnected to your IdP, which may cause disruption if you use team sync to manage access to organizations or licenses from your IdP. We recommend you use the "External groups" endpoints of the REST API to gather information about your teams setup before you migrate, and to reinstate connections afterwards. For more information, see [AUTOTITLE](/rest/teams/external-groups). diff --git a/data/reusables/enterprise_user_management/scim-manages-user-lifecycle.md b/data/reusables/enterprise_user_management/scim-manages-user-lifecycle.md index efe68a83c7e5..16d3f4333893 100644 --- a/data/reusables/enterprise_user_management/scim-manages-user-lifecycle.md +++ b/data/reusables/enterprise_user_management/scim-manages-user-lifecycle.md @@ -6,5 +6,5 @@ With SCIM, you manage the lifecycle of user accounts from your IdP: * If you reassign a user to the IdP application or reactivate their account on your IdP, the user account will be reactivated, and the username will be restored. {% ifversion ghec or ghes > 3.13 %} -To configure team and organization membership, repository access, and permissions on {% data variables.product.product_name %}, you can use groups on your IdP. For more information, see "[AUTOTITLE](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/managing-team-memberships-with-identity-provider-groups)." +To configure team and organization membership, repository access, and permissions on {% data variables.product.product_name %}, you can use groups on your IdP. For more information, see [AUTOTITLE](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/managing-team-memberships-with-identity-provider-groups). {% endif %} diff --git a/data/reusables/files/choose-commit-email.md b/data/reusables/files/choose-commit-email.md index e8da0f234971..cf11b47c6ef1 100644 --- a/data/reusables/files/choose-commit-email.md +++ b/data/reusables/files/choose-commit-email.md @@ -1,5 +1,5 @@ {%- ifversion fpt or ghec %} -1. If you have more than one email address associated with your account on {% data variables.product.prodname_dotcom %}, click the email address drop-down menu and select the email address to use as the Git author email address. Only verified email addresses appear in this drop-down menu. If you enabled email address privacy, then a no-reply will be the default commit author email address. For more information about the exact form the no-reply email address can take, see "[AUTOTITLE](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-your-commit-email-address)." +1. If you have more than one email address associated with your account on {% data variables.product.prodname_dotcom %}, click the email address drop-down menu and select the email address to use as the Git author email address. Only verified email addresses appear in this drop-down menu. If you enabled email address privacy, then a no-reply will be the default commit author email address. For more information about the exact form the no-reply email address can take, see [AUTOTITLE](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-your-commit-email-address). ![Screenshot of a {% data variables.product.prodname_dotcom %} pull request showing a dropdown menu with options to choose the commit author email address. octocat@github.com is selected.](/assets/images/help/repository/choose-commit-email-address.png) {%- endif %} diff --git a/data/reusables/files/choose_commit_branch.md b/data/reusables/files/choose_commit_branch.md index ad0dad44ea14..852683542363 100644 --- a/data/reusables/files/choose_commit_branch.md +++ b/data/reusables/files/choose_commit_branch.md @@ -1,3 +1,3 @@ -1. Below the commit message fields, decide whether to add your commit to the current branch or to a new branch. If your current branch is the default branch, you should choose to create a new branch for your commit and then create a pull request. For more information, see "[AUTOTITLE](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request)." +1. Below the commit message fields, decide whether to add your commit to the current branch or to a new branch. If your current branch is the default branch, you should choose to create a new branch for your commit and then create a pull request. For more information, see [AUTOTITLE](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request). ![Screenshot of a {% data variables.product.prodname_dotcom %} pull request showing a radio button to commit directly to the main branch or to create a new branch. New branch is selected.](/assets/images/help/repository/choose-commit-branch.png) diff --git a/data/reusables/files/commit-author-email-options.md b/data/reusables/files/commit-author-email-options.md index bbd1b696eefa..cd7e1024b7d1 100644 --- a/data/reusables/files/commit-author-email-options.md +++ b/data/reusables/files/commit-author-email-options.md @@ -1,3 +1,3 @@ {% ifversion fpt or ghec %} -If you haven't enabled email address privacy, you can choose which verified email address to author changes with when you edit, delete, or create files or merge a pull request on {% data variables.product.product_name %}. If you enabled email address privacy, then the commit author email address cannot be changed and will be a no-reply by default. For more information about the exact form the no-reply email address can take, see "[AUTOTITLE](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-your-commit-email-address)." +If you haven't enabled email address privacy, you can choose which verified email address to author changes with when you edit, delete, or create files or merge a pull request on {% data variables.product.product_name %}. If you enabled email address privacy, then the commit author email address cannot be changed and will be a no-reply by default. For more information about the exact form the no-reply email address can take, see [AUTOTITLE](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-your-commit-email-address). {% endif %} diff --git a/data/reusables/files/commit-message.md b/data/reusables/files/commit-message.md index c34e5f604ca9..e45ff9e179ce 100644 --- a/data/reusables/files/commit-message.md +++ b/data/reusables/files/commit-message.md @@ -1 +1 @@ -1. In the "Commit message" field, type a short, meaningful commit message that describes the change you made to the file. You can attribute the commit to more than one author in the commit message. For more information, see "[AUTOTITLE](/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors)." +1. In the "Commit message" field, type a short, meaningful commit message that describes the change you made to the file. You can attribute the commit to more than one author in the commit message. For more information, see [AUTOTITLE](/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors). diff --git a/data/reusables/files/delete_branch.md b/data/reusables/files/delete_branch.md index f190ebf954b7..a28e43c25bb8 100644 --- a/data/reusables/files/delete_branch.md +++ b/data/reusables/files/delete_branch.md @@ -1 +1 @@ -1. Optionally, delete the branch. For more information, see "[AUTOTITLE](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository)." +1. Optionally, delete the branch. For more information, see [AUTOTITLE](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository). diff --git a/data/reusables/files/merge_pull_request.md b/data/reusables/files/merge_pull_request.md index ef861d070717..65a6f7584e62 100644 --- a/data/reusables/files/merge_pull_request.md +++ b/data/reusables/files/merge_pull_request.md @@ -1 +1 @@ -1. Click **Merge pull request**. For more information, see "[AUTOTITLE](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request)." +1. Click **Merge pull request**. For more information, see [AUTOTITLE](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request). diff --git a/data/reusables/files/write_commit_message.md b/data/reusables/files/write_commit_message.md index e26568855c00..897b4c292a53 100644 --- a/data/reusables/files/write_commit_message.md +++ b/data/reusables/files/write_commit_message.md @@ -1,4 +1,4 @@ {% ifversion code-view-ui %} 1. Click **Commit changes...** {% endif %} -1. In the "Commit message" field, type a short, meaningful commit message that describes the change you made to the file. You can attribute the commit to more than one author in the commit message. For more information, see "[AUTOTITLE](/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors)." +1. In the "Commit message" field, type a short, meaningful commit message that describes the change you made to the file. You can attribute the commit to more than one author in the commit message. For more information, see [AUTOTITLE](/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors). diff --git a/data/reusables/gated-features/cluster.md b/data/reusables/gated-features/cluster.md index 32821142a22b..a2dd12567407 100644 --- a/data/reusables/gated-features/cluster.md +++ b/data/reusables/gated-features/cluster.md @@ -1 +1 @@ -{% data variables.product.company_short %} determines eligibility for clustering, and must enable the configuration for your instance's license. Clustering requires careful planning and additional administrative overhead. For more information, see "[AUTOTITLE](/admin/enterprise-management/configuring-clustering/about-clustering)." +{% data variables.product.company_short %} determines eligibility for clustering, and must enable the configuration for your instance's license. Clustering requires careful planning and additional administrative overhead. For more information, see [AUTOTITLE](/admin/enterprise-management/configuring-clustering/about-clustering). diff --git a/data/reusables/gated-features/code-review-assignment.md b/data/reusables/gated-features/code-review-assignment.md index 0c72d4db5641..cb18c0ec267b 100644 --- a/data/reusables/gated-features/code-review-assignment.md +++ b/data/reusables/gated-features/code-review-assignment.md @@ -1 +1 @@ -Code review settings are available in all public repositories owned by an organization, and all private repositories owned by organizations on {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_server %}, and {% data variables.product.prodname_ghe_cloud %}. For more information, see "[AUTOTITLE](/get-started/learning-about-github/githubs-plans)." +Code review settings are available in all public repositories owned by an organization, and all private repositories owned by organizations on {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_server %}, and {% data variables.product.prodname_ghe_cloud %}. For more information, see [AUTOTITLE](/get-started/learning-about-github/githubs-plans). diff --git a/data/reusables/gated-features/codespaces-classroom-articles.md b/data/reusables/gated-features/codespaces-classroom-articles.md index ab0c01198373..2b82acaead85 100644 --- a/data/reusables/gated-features/codespaces-classroom-articles.md +++ b/data/reusables/gated-features/codespaces-classroom-articles.md @@ -1 +1 @@ -{% data variables.product.prodname_github_codespaces %} is available to use with {% data variables.product.prodname_classroom %} for organizations that use {% data variables.product.prodname_team %}. To find out if you qualify for a free upgrade to {% data variables.product.prodname_team %}, see "[AUTOTITLE](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-education-for-teachers/apply-to-github-education-as-a-teacher)." +{% data variables.product.prodname_github_codespaces %} is available to use with {% data variables.product.prodname_classroom %} for organizations that use {% data variables.product.prodname_team %}. To find out if you qualify for a free upgrade to {% data variables.product.prodname_team %}, see [AUTOTITLE](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-education-for-teachers/apply-to-github-education-as-a-teacher). diff --git a/data/reusables/gated-features/codespaces-org.md b/data/reusables/gated-features/codespaces-org.md index bef77b6c2727..4c99f8e5c88e 100644 --- a/data/reusables/gated-features/codespaces-org.md +++ b/data/reusables/gated-features/codespaces-org.md @@ -1 +1 @@ -Organizations on {% data variables.product.prodname_team %} and {% data variables.product.prodname_enterprise %} plans can pay for members' and collaborators' use of {% data variables.product.prodname_github_codespaces %}. These organizations can then access settings and policies to manage codespaces paid for by the organization. For more information, see "[AUTOTITLE](/codespaces/managing-codespaces-for-your-organization/choosing-who-owns-and-pays-for-codespaces-in-your-organization#about-ownership-of-codespaces)" and "[AUTOTITLE](/get-started/learning-about-github/githubs-plans)." +Organizations on {% data variables.product.prodname_team %} and {% data variables.product.prodname_enterprise %} plans can pay for members' and collaborators' use of {% data variables.product.prodname_github_codespaces %}. These organizations can then access settings and policies to manage codespaces paid for by the organization. For more information, see [AUTOTITLE](/codespaces/managing-codespaces-for-your-organization/choosing-who-owns-and-pays-for-codespaces-in-your-organization#about-ownership-of-codespaces) and [AUTOTITLE](/get-started/learning-about-github/githubs-plans). diff --git a/data/reusables/gated-features/codespaces-repo.md b/data/reusables/gated-features/codespaces-repo.md index 412e974d12e4..45ee3bd6cec3 100644 --- a/data/reusables/gated-features/codespaces-repo.md +++ b/data/reusables/gated-features/codespaces-repo.md @@ -1,3 +1,3 @@ Repository-level settings for {% data variables.product.prodname_github_codespaces %} are available for all repositories owned by personal accounts.

-For repositories owned by organizations, repository-level settings for {% data variables.product.prodname_github_codespaces %} are available for organizations on {% data variables.product.prodname_team %} and {% data variables.product.prodname_enterprise %} plans. To access the settings, the organization or its parent enterprise must have added a payment method and set a spending limit for {% data variables.product.prodname_github_codespaces %}. For more information, see "[AUTOTITLE](/codespaces/managing-codespaces-for-your-organization/choosing-who-owns-and-pays-for-codespaces-in-your-organization)" and "[AUTOTITLE](/get-started/learning-about-github/githubs-plans)." +For repositories owned by organizations, repository-level settings for {% data variables.product.prodname_github_codespaces %} are available for organizations on {% data variables.product.prodname_team %} and {% data variables.product.prodname_enterprise %} plans. To access the settings, the organization or its parent enterprise must have added a payment method and set a spending limit for {% data variables.product.prodname_github_codespaces %}. For more information, see [AUTOTITLE](/codespaces/managing-codespaces-for-your-organization/choosing-who-owns-and-pays-for-codespaces-in-your-organization) and [AUTOTITLE](/get-started/learning-about-github/githubs-plans). diff --git a/data/reusables/gated-features/delegated-bypass.md b/data/reusables/gated-features/delegated-bypass.md index dee876fb33bf..ba1cb7223c91 100644 --- a/data/reusables/gated-features/delegated-bypass.md +++ b/data/reusables/gated-features/delegated-bypass.md @@ -1,4 +1,4 @@ -Delegated bypass requires push protection to be enabled for the organization or the repository. See "[AUTOTITLE](/code-security/secret-scanning/introduction/about-push-protection)." +Delegated bypass requires push protection to be enabled for the organization or the repository. See [AUTOTITLE](/code-security/secret-scanning/introduction/about-push-protection). Delegated bypass is available for the following repositories: diff --git a/data/reusables/gated-features/display-names.md b/data/reusables/gated-features/display-names.md index d3ec098710fa..812fe5cdf321 100644 --- a/data/reusables/gated-features/display-names.md +++ b/data/reusables/gated-features/display-names.md @@ -1 +1 @@ -Allowing members to see comment authors' profile names is available with {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_server %}, and {% data variables.product.prodname_ghe_cloud %}. For more information, see "[AUTOTITLE](/get-started/learning-about-github/githubs-plans)." +Allowing members to see comment authors' profile names is available with {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_server %}, and {% data variables.product.prodname_ghe_cloud %}. For more information, see [AUTOTITLE](/get-started/learning-about-github/githubs-plans). diff --git a/data/reusables/gated-features/emus.md b/data/reusables/gated-features/emus.md index d50d56ff8638..596cce27d0e0 100644 --- a/data/reusables/gated-features/emus.md +++ b/data/reusables/gated-features/emus.md @@ -1,5 +1,5 @@ {% ifversion ghec %} -{% data variables.product.prodname_emus %} is available for new enterprise accounts on {% data variables.product.prodname_ghe_cloud %}. See "[AUTOTITLE](/enterprise-cloud@latest/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users)." +{% data variables.product.prodname_emus %} is available for new enterprise accounts on {% data variables.product.prodname_ghe_cloud %}. See [AUTOTITLE](/enterprise-cloud@latest/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users). {% endif %} diff --git a/data/reusables/gated-features/generated-health-checks.md b/data/reusables/gated-features/generated-health-checks.md index 53374a57556b..18bcc91c95f6 100644 --- a/data/reusables/gated-features/generated-health-checks.md +++ b/data/reusables/gated-features/generated-health-checks.md @@ -1 +1 @@ -Generating a Health Check is available with {% data variables.contact.premium_support %}. For more information, see "[AUTOTITLE](/support/learning-about-github-support/about-github-premium-support)." +Generating a Health Check is available with {% data variables.contact.premium_support %}. For more information, see [AUTOTITLE](/support/learning-about-github-support/about-github-premium-support). diff --git a/data/reusables/gated-features/ghas-ghec.md b/data/reusables/gated-features/ghas-ghec.md index c490a5f9f720..755c9b2b0f73 100644 --- a/data/reusables/gated-features/ghas-ghec.md +++ b/data/reusables/gated-features/ghas-ghec.md @@ -1,3 +1,3 @@ -{% data variables.product.prodname_GH_advanced_security %} is available for enterprise accounts on {% data variables.product.prodname_ghe_cloud %}.{% ifversion fpt or ghec %} Some features of {% data variables.product.prodname_GH_advanced_security %} are also available for public repositories on {% data variables.product.prodname_dotcom %}. For more information, see "[AUTOTITLE](/get-started/learning-about-github/githubs-plans)."{% endif %} +{% data variables.product.prodname_GH_advanced_security %} is available for enterprise accounts on {% data variables.product.prodname_ghe_cloud %}.{% ifversion fpt or ghec %} Some features of {% data variables.product.prodname_GH_advanced_security %} are also available for public repositories on {% data variables.product.prodname_dotcom %}. For more information, see [AUTOTITLE](/get-started/learning-about-github/githubs-plans).{% endif %} {% data reusables.advanced-security.ghas-for-azdo-link %} diff --git a/data/reusables/gated-features/ghas.md b/data/reusables/gated-features/ghas.md index a67b1d5c0776..25d238c4b0a3 100644 --- a/data/reusables/gated-features/ghas.md +++ b/data/reusables/gated-features/ghas.md @@ -1,3 +1,3 @@ -{% data variables.product.prodname_GH_advanced_security %} is available for enterprise accounts on {% data variables.product.prodname_ghe_cloud %} and {% data variables.product.prodname_ghe_server %}.{% ifversion fpt or ghec %} Some features of {% data variables.product.prodname_GH_advanced_security %} are also available for public repositories on {% data variables.product.prodname_dotcom %}.{% endif %} For more information, see "[AUTOTITLE](/get-started/learning-about-github/githubs-plans)." +{% data variables.product.prodname_GH_advanced_security %} is available for enterprise accounts on {% data variables.product.prodname_ghe_cloud %} and {% data variables.product.prodname_ghe_server %}.{% ifversion fpt or ghec %} Some features of {% data variables.product.prodname_GH_advanced_security %} are also available for public repositories on {% data variables.product.prodname_dotcom %}.{% endif %} For more information, see [AUTOTITLE](/get-started/learning-about-github/githubs-plans). {% data reusables.advanced-security.ghas-for-azdo-link %} diff --git a/data/reusables/gated-features/more-info-org-products.md b/data/reusables/gated-features/more-info-org-products.md index 7913778d01c9..16baddaae07e 100644 --- a/data/reusables/gated-features/more-info-org-products.md +++ b/data/reusables/gated-features/more-info-org-products.md @@ -1 +1 @@ -{% ifversion fpt or ghec %}For more information, see "[AUTOTITLE](/get-started/learning-about-github/githubs-plans)."{% endif %} +{% ifversion fpt or ghec %}For more information, see [AUTOTITLE](/get-started/learning-about-github/githubs-plans).{% endif %} diff --git a/data/reusables/gated-features/more-info.md b/data/reusables/gated-features/more-info.md index 7913778d01c9..16baddaae07e 100644 --- a/data/reusables/gated-features/more-info.md +++ b/data/reusables/gated-features/more-info.md @@ -1 +1 @@ -{% ifversion fpt or ghec %}For more information, see "[AUTOTITLE](/get-started/learning-about-github/githubs-plans)."{% endif %} +{% ifversion fpt or ghec %}For more information, see [AUTOTITLE](/get-started/learning-about-github/githubs-plans).{% endif %} diff --git a/data/reusables/gated-features/packages.md b/data/reusables/gated-features/packages.md index b960a78e0974..f08328788cb3 100644 --- a/data/reusables/gated-features/packages.md +++ b/data/reusables/gated-features/packages.md @@ -1,6 +1,6 @@ {% ifversion fpt or ghec %} -{% data variables.product.prodname_registry %} is available with {% data variables.product.prodname_free_user %}, {% data variables.product.prodname_pro %}, {% data variables.product.prodname_free_team %} for organizations, {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_cloud %}, and {% data variables.product.prodname_ghe_server %} 3.0 or higher.{% ifversion ghes %} For more information about upgrading your {% data variables.product.prodname_ghe_server %} instance, see "[AUTOTITLE](/admin/overview/about-upgrades-to-new-releases)" and refer to the [{% data variables.enterprise.upgrade_assistant %}](https://support.github.com/enterprise/server-upgrade) to find the upgrade path from your current release version.{% endif %} +{% data variables.product.prodname_registry %} is available with {% data variables.product.prodname_free_user %}, {% data variables.product.prodname_pro %}, {% data variables.product.prodname_free_team %} for organizations, {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_cloud %}, and {% data variables.product.prodname_ghe_server %} 3.0 or higher.{% ifversion ghes %} For more information about upgrading your {% data variables.product.prodname_ghe_server %} instance, see [AUTOTITLE](/admin/overview/about-upgrades-to-new-releases) and refer to the [{% data variables.enterprise.upgrade_assistant %}](https://support.github.com/enterprise/server-upgrade) to find the upgrade path from your current release version.{% endif %} {% ifversion fpt or ghec %} -
{% data variables.product.prodname_registry %} is not available for private repositories owned by accounts using legacy per-repository plans. Also, accounts using legacy per-repository plans cannot access registries that support granular permissions, because these accounts are billed by repository.{% ifversion ghec %} {% data variables.product.prodname_emus %} do not have individual storage allocation to publish packages within their account's namespace, but can publish to an organization's namespace. For additional information on {% data variables.product.prodname_emus %}, see "[AUTOTITLE](/admin/managing-iam/understanding-iam-for-enterprises/about-enterprise-managed-users)."{% endif %} For the list of registries that support granular permissions, see "[AUTOTITLE](/packages/learn-github-packages/about-permissions-for-github-packages#granular-permissions-for-userorganization-scoped-packages)." {% data reusables.gated-features.more-info %} +
{% data variables.product.prodname_registry %} is not available for private repositories owned by accounts using legacy per-repository plans. Also, accounts using legacy per-repository plans cannot access registries that support granular permissions, because these accounts are billed by repository.{% ifversion ghec %} {% data variables.product.prodname_emus %} do not have individual storage allocation to publish packages within their account's namespace, but can publish to an organization's namespace. For additional information on {% data variables.product.prodname_emus %}, see [AUTOTITLE](/admin/managing-iam/understanding-iam-for-enterprises/about-enterprise-managed-users).{% endif %} For the list of registries that support granular permissions, see [AUTOTITLE](/packages/learn-github-packages/about-permissions-for-github-packages#granular-permissions-for-userorganization-scoped-packages). {% data reusables.gated-features.more-info %} {% endif %} {% endif %} diff --git a/data/reusables/gated-features/pages.md b/data/reusables/gated-features/pages.md index 94ceae037c62..7128d564baa5 100644 --- a/data/reusables/gated-features/pages.md +++ b/data/reusables/gated-features/pages.md @@ -1,3 +1,3 @@ {% data variables.product.prodname_pages %} is available in public repositories with {% data variables.product.prodname_free_user %} and {% data variables.product.prodname_free_team %} for organizations, and in public and private repositories with {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_cloud %}, and {% data variables.product.prodname_ghe_server %}. {% ifversion fpt or ghec %}{% data reusables.gated-features.more-info %}{% endif %} -{% ifversion fpt or ghec %}{% data variables.product.prodname_pages %} now uses {% data variables.product.prodname_actions %} to execute the Jekyll build. When using a branch as the source of your build, {% data variables.product.prodname_actions %} must be enabled in your repository if you want to use the built-in Jekyll workflow. Alternatively, if {% data variables.product.prodname_actions %} is unavailable or disabled, adding a `.nojekyll` file to the root of your source branch will bypass the Jekyll build process and deploy the content directly. For more information on enabling {% data variables.product.prodname_actions %}, see "[AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository)."{% endif %} +{% ifversion fpt or ghec %}{% data variables.product.prodname_pages %} now uses {% data variables.product.prodname_actions %} to execute the Jekyll build. When using a branch as the source of your build, {% data variables.product.prodname_actions %} must be enabled in your repository if you want to use the built-in Jekyll workflow. Alternatively, if {% data variables.product.prodname_actions %} is unavailable or disabled, adding a `.nojekyll` file to the root of your source branch will bypass the Jekyll build process and deploy the content directly. For more information on enabling {% data variables.product.prodname_actions %}, see [AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository).{% endif %} diff --git a/data/reusables/gated-features/repository-insights.md b/data/reusables/gated-features/repository-insights.md index d39ebe7079b1..b36679dc5c7d 100644 --- a/data/reusables/gated-features/repository-insights.md +++ b/data/reusables/gated-features/repository-insights.md @@ -1 +1 @@ -This repository insights graph is available in public repositories with {% data variables.product.prodname_free_user %} and {% data variables.product.prodname_free_team %} for organizations, and in public and private repositories with {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_cloud %}, and {% data variables.product.prodname_ghe_server %}.{% ifversion fpt or ghec %} For more information, see "[AUTOTITLE](/repositories/viewing-activity-and-data-for-your-repository/about-repository-graphs)" and "[AUTOTITLE](/get-started/learning-about-github/githubs-plans)."{% endif %} +This repository insights graph is available in public repositories with {% data variables.product.prodname_free_user %} and {% data variables.product.prodname_free_team %} for organizations, and in public and private repositories with {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_cloud %}, and {% data variables.product.prodname_ghe_server %}.{% ifversion fpt or ghec %} For more information, see [AUTOTITLE](/repositories/viewing-activity-and-data-for-your-repository/about-repository-graphs) and [AUTOTITLE](/get-started/learning-about-github/githubs-plans).{% endif %} diff --git a/data/reusables/gated-features/restrict-email-domain.md b/data/reusables/gated-features/restrict-email-domain.md index eed0377b4282..b17d82c6c6e6 100644 --- a/data/reusables/gated-features/restrict-email-domain.md +++ b/data/reusables/gated-features/restrict-email-domain.md @@ -1 +1 @@ -Restriction of email notifications to approved or verified domains is available with {% data variables.product.prodname_ghe_cloud %} and {% data variables.product.prodname_ghe_server %}. For more information, see "[AUTOTITLE](/get-started/learning-about-github/githubs-plans)." +Restriction of email notifications to approved or verified domains is available with {% data variables.product.prodname_ghe_cloud %} and {% data variables.product.prodname_ghe_server %}. For more information, see [AUTOTITLE](/get-started/learning-about-github/githubs-plans). diff --git a/data/reusables/gated-features/verify-and-approve-domain.md b/data/reusables/gated-features/verify-and-approve-domain.md index 2c0ee90114a9..e7e05b554d64 100644 --- a/data/reusables/gated-features/verify-and-approve-domain.md +++ b/data/reusables/gated-features/verify-and-approve-domain.md @@ -1 +1 @@ -Verification and approval of domains is available with {% data variables.product.prodname_ghe_cloud %} and {% data variables.product.prodname_ghe_server %}. For more information, see "[AUTOTITLE](/get-started/learning-about-github/githubs-plans)." +Verification and approval of domains is available with {% data variables.product.prodname_ghe_cloud %} and {% data variables.product.prodname_ghe_server %}. For more information, see [AUTOTITLE](/get-started/learning-about-github/githubs-plans).