[pull] main from github:main

content/account-and-profile/concepts/index.md

@@ -17,4 +17,5 @@ children:
   - /changing-your-github-username
   - /email-addresses
   - /scheduled-reminders
+  - /personal-repository-access-and-collaboration
 ---

content/account-and-profile/concepts/personal-repository-access-and-collaboration.md

@@ -0,0 +1,48 @@
+---
+title: Personal repository access and collaboration
+intro: 'Learn how to manage access and collaboration for repositories you own with your personal account on {% data variables.product.github %}.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
+topics:
+  - Accounts
+  - Repositories
+  - Privacy
+  - Open Source
+shortTitle: Access to repositories
+---
+
+## About collaboration in a personal repository
+
+You can collaborate with others on repositories you own by inviting them as collaborators. Collaborators have access to contribute to your code and manage issues and pull requests.
+
+{% ifversion ghec %}
+
+If you're a member of an {% data variables.enterprise.prodname_emu_enterprise %}, you can only invite other members of your enterprise to collaborate with you. {% data reusables.enterprise-accounts.emu-more-info-account %}
+
+{% endif %}
+
+To add a collaborator, see [AUTOTITLE](/account-and-profile/how-tos/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository).
+
+{% ifversion fpt or ghec %}
+
+{% data reusables.repositories.private_forks_inherit_permissions %}
+
+## About successors
+
+We recommend inviting another {% data variables.product.company_short %} user to be your successor, to manage your user owned repositories if you cannot. As a successor, they will have permission to:
+
+* Archive your public repositories.
+* Transfer your public repositories to their own user owned account.
+* Transfer your public repositories to an organization where they can create repositories.
+
+Successors cannot log into your account.
+
+An appointed successor can manage your public repositories after presenting a death certificate then waiting for 7 days or presenting an obituary then waiting for 21 days. For more information, see [AUTOTITLE](/free-pro-team@latest/site-policy/other-site-policies/github-deceased-user-policy).
+
+To request access to manage repositories as a successor, please contact us through the {% data variables.contact.contact_support_portal %}.
+
+For more information, see [AUTOTITLE](/account-and-profile/how-tos/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-personal-accounts-repositories).
+
+{% endif %}

content/account-and-profile/how-tos/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/index.md

@@ -21,6 +21,6 @@ children:
   - /removing-a-collaborator-from-a-personal-repository
   - /removing-yourself-from-a-collaborators-repository
   - /maintaining-ownership-continuity-of-your-personal-accounts-repositories
-shortTitle: Access to your repositories
+shortTitle: Manage repository access
 ---
 

content/account-and-profile/how-tos/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md

@@ -19,30 +19,11 @@ topics:
   - Repositories
 shortTitle: Invite collaborators
 ---
-## About collaboration in a personal repository
-
-To collaborate with users in a repository that belongs to your personal account on {% data variables.product.prodname_dotcom %}, you can invite the users as collaborators.
-
-If you want to grant more granular access to the repository, you can create a repository within an organization. For more information, see [AUTOTITLE](/get-started/learning-about-github/access-permissions-on-github).
-
-{% ifversion ghec %}
-
-If you're a member of an {% data variables.enterprise.prodname_emu_enterprise %}, you can only invite other members of your enterprise to collaborate with you. {% data reusables.enterprise-accounts.emu-more-info-account %}
-
-{% endif %}
-
-{% data reusables.repositories.private_forks_inherit_permissions %}
 
 ## Inviting a collaborator to a personal repository
 
 You can send an invitation to collaborate in your repository directly to someone on {% data variables.product.prodname_dotcom %}{% ifversion fpt or ghec %}, or to the person's email address{% elsif ghes %}.{% endif %}.
 
-{% ifversion fpt or ghec %}
-
-{% data variables.product.company_short %} limits the number of people who can be invited to a repository within a 24-hour period. If you exceed this limit, either wait 24 hours or create an organization to collaborate with more people. For more information, see [AUTOTITLE](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch).
-
-{% endif %}
-
 1. Ask for the username of the person you're inviting as a collaborator.{% ifversion fpt or ghec %} If they don't have a username yet, they can sign up for {% data variables.product.prodname_dotcom %}. For more information, see [AUTOTITLE](/get-started/start-your-journey/creating-an-account-on-github).{% endif %}
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
@@ -54,9 +35,6 @@ You can send an invitation to collaborate in your repository directly to someone
 1. The user will receive an email inviting them to the repository. Once they accept your invitation, they will have collaborator access to your repository.
 {% endif %}
 
-## Further reading
+## Next steps
 
-* [AUTOTITLE](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-user-account-settings/permission-levels-for-a-personal-account-repository#collaborator-access-for-a-repository-owned-by-a-personal-account)
-* [AUTOTITLE](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository)
-* [AUTOTITLE](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository)
-* [AUTOTITLE](/organizations/organizing-members-into-teams)
+* For reference information, see [AUTOTITLE](/account-and-profile/reference/permission-levels-for-a-personal-account-repository#collaborator-access-for-a-repository-owned-by-a-personal-account)

content/account-and-profile/how-tos/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-personal-accounts-repositories.md

@@ -14,19 +14,6 @@ redirect_from:
   - /account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-personal-accounts-repositories
 shortTitle: Ownership continuity
 ---
-## About successors
-
-We recommend inviting another {% data variables.product.company_short %} user to be your successor, to manage your user owned repositories if you cannot. As a successor, they will have permission to:
-
-* Archive your public repositories.
-* Transfer your public repositories to their own user owned account.
-* Transfer your public repositories to an organization where they can create repositories.
-
-Successors cannot log into your account.
-
-An appointed successor can manage your public repositories after presenting a death certificate then waiting for 7 days or presenting an obituary then waiting for 21 days. For more information, see [AUTOTITLE](/free-pro-team@latest/site-policy/other-site-policies/github-deceased-user-policy).
-
-To request access to manage repositories as a successor, please contact us through the {% data variables.contact.contact_support_portal %}.
 
 ## Inviting a successor
 

content/account-and-profile/how-tos/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository.md

@@ -1,6 +1,6 @@
 ---
 title: Removing a collaborator from a personal repository
-intro: 'When you remove a collaborator from your project, they lose read/write access to your repository. If the repository is private and the person has created a fork, then that fork is also deleted.'
+intro: 'You can remove a collaborator from your personal repository at any time.'
 redirect_from:
   - /articles/how-do-i-remove-a-collaborator
   - /articles/what-happens-when-i-remove-a-collaborator-from-my-private-repository
@@ -22,9 +22,6 @@ topics:
   - Repositories
 shortTitle: Remove a collaborator
 ---
-## Deleting forks of private repositories
-
-While forks of private repositories are deleted when a collaborator is removed, the person will still retain any local clones of your repository.
 
 ## Removing collaborator permissions from a person contributing to a repository
 
@@ -33,7 +30,6 @@ While forks of private repositories are deleted when a collaborator is removed,
 {% data reusables.repositories.click-collaborators-teams %}
 1. To the right of the collaborator you want to remove, click **Remove**.
 
-## Further reading
+## Next steps
 
-* [AUTOTITLE](/organizations/organizing-members-into-teams/removing-organization-members-from-a-team)
-* [AUTOTITLE](/organizations/managing-user-access-to-your-organizations-repositories/managing-outside-collaborators/removing-an-outside-collaborator-from-an-organization-repository)
+* For reference information, see [AUTOTITLE](/account-and-profile/reference/permission-levels-for-a-personal-account-repository#removing-a-collaborator).

content/account-and-profile/reference/permission-levels-for-a-personal-account-repository.md

@@ -66,6 +66,12 @@ The repository owner has full control of the repository. In addition to the acti
 
 ## Collaborator access for a repository owned by a personal account
 
+{% ifversion fpt or ghec %}
+
+{% data variables.product.company_short %} limits the number of people who can be invited to a repository within a 24-hour period. If you exceed this limit, either wait 24 hours or create an organization to collaborate with more people. For more information, see [AUTOTITLE](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch).
+
+{% endif %}
+
 Collaborators on a personal repository can pull (read) the contents of the repository and push (write) changes to the repository.
 
 > [!NOTE]
@@ -95,6 +101,10 @@ Collaborators can also perform the following actions.
 | {% endif %} |
 | Remove themselves as collaborators on the repository | [AUTOTITLE](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository) |
 
-## Further reading
+If you want more granular control of permissions to the repository, you can create a repository within an organization. For more information, see [AUTOTITLE](/get-started/learning-about-github/access-permissions-on-github).
+
+## Removing a collaborator
+
+While forks of private repositories are deleted when a collaborator is removed, the person will still retain any local clones of your repository.
 
-* [AUTOTITLE](/organizations/managing-user-access-to-your-organizations-repositories/managing-repository-roles/repository-roles-for-an-organization)
+When you remove a collaborator from your project, they lose read/write access to your repository. If the repository is private and the person has created a fork, then that fork is also deleted.

content/actions/how-tos/troubleshoot-workflows.md

@@ -66,7 +66,7 @@ To analyze the efficiency and reliability of your workflows using metrics, see [
 
 ## Troubleshooting workflow triggers
 
-You can review your workflow’s `on:` field to understand what is expected to trigger the workflow. For more information, see [AUTOTITLE](/actions/writing-workflows/choosing-when-your-workflow-runs/triggering-a-workflow).
+You can review your workflow's `on:` field to understand what is expected to trigger the workflow. For more information, see [AUTOTITLE](/actions/writing-workflows/choosing-when-your-workflow-runs/triggering-a-workflow).
 
 For a full list of available events, see [AUTOTITLE](/actions/writing-workflows/choosing-when-your-workflow-runs/events-that-trigger-workflows).
 
@@ -118,4 +118,74 @@ We recommend using unique label names for larger and self-hosted runners. If a l
 
 If you use self-hosted runners, you can view their activity and diagnose common issues.
 
-For more information, see [AUTOTITLE](/actions/hosting-your-own-runners/managing-self-hosted-runners/monitoring-and-troubleshooting-self-hosted-runners).
+For more information, see [AUTOTITLE](/actions/how-tos/manage-runners/self-hosted-runners/monitor-and-troubleshoot).
+
+## Networking troubleshooting suggestions
+
+Our support is limited for network issues that involve:
+
+* Your networks
+* External networks
+* Third-party systems
+* General internet connectivity
+
+To view {% data variables.product.github %}'s realtime platform status, check [{% data variables.product.github %} Status](https://githubstatus.com/).
+
+For other network-related issues, review your organization's network settings and verify the status of any third-party services you're accessing. If problems persist, consider reaching out to your network administrators for further assistance.
+
+If you're unsure about the issue, contact {% data variables.contact.github_support %}. For details on how to contact support, see [AUTOTITLE](/support/contacting-github-support).
+
+### DNS
+
+Issues may occur from Domain Name System (DNS) configuration, resolution, or resolver problems. We recommend you review available logs, vendor documentation, or consult with your administrators for additional assistance.
+
+### Firewalls
+
+Activities may become blocked by firewalls. If this occurs, you may want to review available logs, vendor documentation, or consult with your administrators for additional assistance.
+
+### Proxies
+
+Activities could fail when using a proxy for communications. It's good practice to review available logs, vendor documentation, or consult with your administrators for additional assistance.
+
+Refer to [AUTOTITLE](/actions/how-tos/manage-runners/self-hosted-runners/use-proxy-servers) for information about configuring the runner application to utilize a proxy.
+
+### Subnets
+
+It is possible to encounter issues with subnets in use or overlaps with an existing network, such as within virtual cloud provider or Docker networks. In such cases, we recommend you review your network topology and subnets in use.
+
+### Certificates
+
+Issues may occur from self-signed or custom certificate chains and certificate stores. You can check that a certificate in use has not expired and is currently trusted. Certificates may be inspected with `curl` or similar tools. You can also review available logs, vendor documentation, or consult with your administrators for additional assistance.
+
+### IP lists
+
+IP allow or deny lists may disrupt expected communications. If there is a problem, you should review available logs, vendor documentation, or consult with your administrators for additional assistance.
+
+{% ifversion ghec %}
+If your {% data variables.product.github %} account is configured with an IP allowlist, workflows will fail if a runner uses an IP address that isn’t included in the allowlist. To resolve this, verify that the runner's IP addresses are added to your organization's or enterprise's allowlist. For more details, see [AUTOTITLE](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-allowed-ip-addresses-for-your-organization) and/or [AUTOTITLE](/admin/configuring-settings/hardening-security-for-your-enterprise/restricting-network-traffic-to-your-enterprise-with-an-ip-allow-list).
+{% endif %}
+
+{% ifversion fpt or ghec %}
+For information on {% data variables.product.github %}'s IP addresses, such as those used by {% data variables.product.github %}-hosted runners, see [AUTOTITLE](/authentication/keeping-your-account-and-data-secure/about-githubs-ip-addresses).
+
+Static IP addresses are available for use with {% data variables.product.github %}-hosted larger runners. See [AUTOTITLE](/actions/how-tos/manage-runners/larger-runners/manage-larger-runners) for more information.
+{% endif %}
+
+### Operating systems and software applications
+
+In addition to firewalls or proxies, customizations performed to {% data variables.product.github %}-hosted runners, such as installing additional software packages, may result in communication disruptions. For information about available customization options, see [AUTOTITLE](/actions/how-tos/manage-runners/github-hosted-runners/customize-runners).
+
+* For self-hosted runners, learn more about necessary endpoints in [AUTOTITLE](/actions/reference/runners/self-hosted-runners).
+
+* For help configuring WireGuard, see [AUTOTITLE](/actions/how-tos/manage-runners/github-hosted-runners/connect-to-a-private-network/connect-with-wireguard).
+
+* For details about configuring OpenID Connect (OIDC), see [AUTOTITLE](/actions/how-tos/manage-runners/github-hosted-runners/connect-to-a-private-network/connect-with-oidc).
+{% ifversion fpt or ghec %}
+
+### Azure private networking for {% data variables.product.github %}-hosted runners
+
+Issues may arise from the use of {% data variables.product.github %}-hosted runners within your configured Azure Virtual Networks (VNETs) settings.
+
+For troubleshooting advice, see [AUTOTITLE](/organizations/managing-organization-settings/troubleshooting-azure-private-network-configurations-for-github-hosted-runners-in-your-organization) or {% ifversion ghec %}[AUTOTITLE](/admin/configuring-settings/configuring-private-networking-for-hosted-compute-products/troubleshooting-azure-private-network-configurations-for-github-hosted-runners-in-your-enterprise){% else %}[AUTOTITLE](/enterprise-cloud@latest/admin/configuring-settings/configuring-private-networking-for-hosted-compute-products/troubleshooting-azure-private-network-configurations-for-github-hosted-runners-in-your-enterprise) in the {% data variables.product.prodname_ghe_cloud %} docs{% endif %}.
+
+{% endif %}

content/admin/administering-your-instance/administering-your-instance-from-the-command-line/command-line-utilities.md

@@ -1005,6 +1005,18 @@ All Storage tests passed
 
 ## High availability
 
+{% ifversion ghes > 3.17 %}
+
+### ghe-repl-decommission
+
+This command decommissions the database entries for the node with the specified UUID. You run this command on the new primary after performing a failover to a replica node, to remove the decommissioned node's database entries. For more information, see [AUTOTITLE](/admin/enterprise-management/configuring-high-availability/initiating-a-failover-to-your-replica-appliance).
+
+```shell
+ghe-repl-decommission <UUID>
+```
+
+{% endif %}
+
 ### ghe-repl-promote
 
 This command disables replication on an existing replica node and converts the replica node to a primary node using the same settings as the original primary node. All replication services are enabled. For more information, see [AUTOTITLE](/admin/enterprise-management/configuring-high-availability/initiating-a-failover-to-your-replica-appliance).

content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity-in-your-enterprise/log-forwarding.md

@@ -25,7 +25,7 @@ Forwarding logs to an external receiver allows your organization to centralize l
 
 Any log collection system that supports syslog-style log streams is supported (e.g., [Logstash](https://www.elastic.co/products/logstash) and [Splunk](https://docs.splunk.com/Documentation/Splunk/latest/Data/Monitornetworkports)).
 
-When you enable log forwarding, you must upload a CA certificate to encrypt communications between syslog endpoints. Your appliance and the remote syslog server will perform two-way SSL, each providing a certificate to the other and validating the certificate which is received.
+When you enable log forwarding, you must upload a CA certificate to encrypt communications between syslog endpoints. Your appliance will establish an SSL connection to the remote syslog server and validate the server’s certificate.
 
 For more information on log content, see [AUTOTITLE](/admin/monitoring-and-managing-your-instance/monitoring-your-instance/about-system-logs).
 

content/admin/monitoring-and-managing-your-instance/configuring-high-availability/initiating-a-failover-to-your-replica-appliance.md

@@ -64,10 +64,10 @@ The time required to failover depends on how long it takes to manually promote t
       cat /data/user/common/uuid
       ```
 
-    * On the new primary, remove the UUIDs using `ghe-repl-teardown`. Please replace `UUID` with a UUID you retrieved in the previous step.
+    * On the new primary, remove the UUIDs using {% ifversion ghes > 3.17 %}`ghe-repl-decommission`{% else %}`ghe-repl-teardown`{% endif %}. Please replace `UUID` with the UUID you retrieved in the previous step.
 
       ```shell
-      ghe-repl-teardown -u UUID
+      {% ifversion ghes > 3.17 %}ghe-repl-decommission UUID{% else %}ghe-repl-teardown -u UUID{% endif %}
       ```
 
 ## Further reading