Add Instructions for using SSH on a Regional GHE Instance (#60206)

Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Co-authored-by: mc <42146119+mchammer01@users.noreply.github.com>

Author: 3 people

content/admin/data-residency/feature-overview-for-github-enterprise-cloud-with-data-residency.md

@@ -71,6 +71,7 @@ The following examples are not exhaustive.
 | OIDC trusts for {% data variables.product.prodname_actions %} deployments | The OIDC token is issued from `https://token.actions.githubusercontent.com`. | The OIDC token is issued from `https://token.actions.SUBDOMAIN.ghe.com` |
 | Raw URLs | `https://raw.githubusercontent.com/` | `https://raw.SUBDOMAIN.ghe.com/` |
 | Anonymized URLs for images and videos | `https://private-user-images.githubusercontent.com/` | `https://SUBDOMAIN.ghe.com/user-attachments/assets/` |
+| Cloning repositories using SSH | `git clone git@github.com:OWNER/REPOSITORY.git` | `git clone SUBDOMAIN@SUBDOMAIN.ghe.com:OWNER/REPOSITORY.git` |
 
 {% endrowheaders %}
 

content/admin/data-residency/network-details-for-ghecom.md

@@ -27,6 +27,14 @@ gh api /meta --hostname octocorp.ghe.com
 
 For more information, see [AUTOTITLE](/rest/meta/meta).
 
+## Using SSH with {% data variables.enterprise.data_residency_site %}
+
+To clone a repository using Git over SSH from `{% data variables.enterprise.data_residency_domain %}`, where SUBDOMAIN is your enterprise's dedicated subdomain on {% data variables.enterprise.data_residency_site %}, use the SUBDOMAIN as the SSH username instead of `git`.
+
+```shell
+git clone SUBDOMAIN@SUBDOMAIN.ghe.com:OWNER/REPO.git
+```
+
 ## {% data variables.product.github %}'s hostnames
 
 * `*.{% data variables.enterprise.data_residency_domain %}`, where SUBDOMAIN is your enterprise's dedicated subdomain on {% data variables.enterprise.data_residency_site %}

content/authentication/connecting-to-github-with-ssh/managing-deploy-keys.md

@@ -103,6 +103,22 @@ For enhanced security and fine-grained control over repository access and permis
 
 You can also use the REST API to create deploy keys. For more information, see [AUTOTITLE](/rest/deploy-keys/deploy-keys).
 
+You can then interact with the repository using SSH. For example:
+
+```bash
+git clone git@{% ifversion fpt or ghec %}github.com{% else %}my-GHE-hostname.com{% endif %}:OWNER/REPO.git
+```
+
+{% ifversion ghec %}
+
+> [!NOTE] {% data reusables.enterprise-data-residency.ssh-user %}
+>
+> ```bash
+> git clone {% data variables.enterprise.data_residency_example_git_ssh %}:OWNER/REPO.git
+> ```
+
+{% endif %}
+
 ### Using multiple repositories on one server
 
 If you use multiple repositories on one server, you will need to generate a dedicated key pair for each one. You can't reuse a deploy key for multiple repositories.

content/authentication/connecting-to-github-with-ssh/testing-your-ssh-connection.md

@@ -69,3 +69,14 @@ You'll need to authenticate this action using your password, which is the SSH ke
    > The remote command should exit with code 1.
 
 1. Verify that the resulting message contains your username. If you receive a "permission denied" message, see [AUTOTITLE](/authentication/troubleshooting-ssh/error-permission-denied-publickey).
+
+{% ifversion ghec or fpt %}
+
+> [!TIP] {% data reusables.enterprise-data-residency.ssh-user %}
+>
+> ```shell
+> ssh -T {% data variables.enterprise.data_residency_example_git_ssh %}
+> # Attempts to ssh to {% data variables.enterprise.data_residency_example_domain %}
+> ```
+
+{% endif %}

content/authentication/troubleshooting-ssh/error-permission-denied-publickey.md

@@ -68,6 +68,17 @@ You should see this output:
 > Hi USERNAME! You've successfully authenticated...
 ```
 
+{% ifversion ghec %}
+
+> [!WARNING]
+> {% data reusables.enterprise-data-residency.ssh-user %}
+>
+> ```shell
+> ssh -T {% data variables.enterprise.data_residency_example_git_ssh %}
+> ```
+
+{% endif %}
+
 ## Make sure you have a key that is being used
 
 {% mac %}

data/reusables/enterprise-data-residency/ssh-user.md

@@ -0,0 +1 @@
+If you are accessing {% data variables.product.github %} at a different domain such as `{% data variables.enterprise.data_residency_example_domain %}`, then you need to replace `git@{% data variables.product.product_url %}` with `{% data variables.enterprise.data_residency_example_git_ssh %}`.

data/variables/enterprise.yml

@@ -16,6 +16,7 @@ data_residency_site: 'GHE.com'
 data_residency_domain: 'SUBDOMAIN.ghe.com'
 data_residency_api: 'api.SUBDOMAIN.ghe.com'
 data_residency_example_domain: 'octocorp.ghe.com'
+data_residency_example_git_ssh: 'octocorp@octocorp.ghe.com'
 
 # GitHub Connect (enterprise accounts, other unified features)
 ## Phrase content so that the uncapitalized unified contributions or unified search variables are not used at the start of a sentence.