Merge pull request github#35062 from github/repo-sync

docs-bot · web-flow · commit 9297004c1fc5 · 2024-10-24T05:34:21.000-04:00
Repo sync
diff --git a/content/index.md b/content/index.md
@@ -100,7 +100,14 @@ childGroups:
       - repositories
       - pull-requests
       - discussions
+  - name: GitHub Copilot
+    octicon: CopilotIcon
+    children:
       - copilot
+      - copilot/using-github-copilot/getting-code-suggestions-in-your-ide-with-github-copilot
+      - copilot/using-github-copilot/prompt-engineering-for-github-copilot
+      - copilot/using-github-copilot/asking-github-copilot-questions-in-githubcom
+      - copilot/using-github-copilot/example-use-cases/refactoring-code-with-github-copilot
   - name: CI/CD and DevOps
     octicon: GearIcon
     children:
@@ -128,21 +135,22 @@ childGroups:
       - issues
       - issues/planning-and-tracking-with-projects
       - search-github
+  - name: Enterprise and Teams
+    octicon: OrganizationIcon
+    children:
+      - organizations
+      - code-security/securing-your-organization
+      - admin
+      - gh-wa
   - name: Developers
     octicon: CodeSquareIcon
     children:
       - apps
       - rest
       - graphql
       - webhooks
+      - copilot/building-copilot-extensions
       - github-models
-  - name: Enterprise and Teams
-    octicon: OrganizationIcon
-    children:
-      - organizations
-      - code-security/securing-your-organization
-      - admin
-      - gh-wa
   - name: Community
     octicon: GlobeIcon
     children:
diff --git a/data/reusables/enterprise_installation/hotpatching-explanation.md b/data/reusables/enterprise_installation/hotpatching-explanation.md
@@ -2,6 +2,6 @@ You can upgrade {% data variables.product.prodname_ghe_server %} to the latest p
 
 You can use hotpatching to upgrade to a newer patch release, but not a feature release. For example, you can upgrade from 2.10.1 to 2.10.5 because they are in the same feature series, but not from 2.10.9 to 2.11.0 because they are in a different feature series.
 
-Hotpatches do not generally require a reboot. If a hotpatch does require a reboot, the {% data variables.product.product_name %} release notes will indicate the requirement.
+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)."
diff --git a/src/landings/components/ProductSelectionCard.tsx b/src/landings/components/ProductSelectionCard.tsx
@@ -10,6 +10,11 @@ type ProductSelectionCardProps = {
 }
 
 export const ProductSelectionCard = ({ group }: ProductSelectionCardProps) => {
+  // Don't display the group if it has no children due to versioning
+  if (!group.children || group.children.length === 0) {
+    return null
+  }
+
   const groupIcon = {
     height: '22px',
   }

Original file line number	Diff line number	Diff line change
`@@ -10,6 +10,11 @@ type ProductSelectionCardProps = {`
`10`	`10`	`}`
`11`	`11`
`12`	`12`	`export const ProductSelectionCard = ({ group }: ProductSelectionCardProps) => {`
	`13`	`+ // Don't display the group if it has no children due to versioning`
	`14`	`+ if (!group.children \|\| group.children.length === 0) {`
	`15`	`+ return null`
	`16`	`+ }`
	`17`	`+`
`13`	`18`	`const groupIcon = {`
`14`	`19`	`height: '22px',`
`15`	`20`	`}`