From 4eb3bc52a837e78640a4cfab331c7eee75115a9e Mon Sep 17 00:00:00 2001 From: Pallavi <96553709+pallsama@users.noreply.github.com> Date: Thu, 24 Oct 2024 01:26:06 -0700 Subject: [PATCH 1/2] Changing wording of reboots during hot patching. (#52476) --- .../enterprise_installation/hotpatching-explanation.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/data/reusables/enterprise_installation/hotpatching-explanation.md b/data/reusables/enterprise_installation/hotpatching-explanation.md index 78fd20a44b09..9eff688e9880 100644 --- 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)." From 51b4cb965e6ed4f62956892e1477d44fc0edb3ef Mon Sep 17 00:00:00 2001 From: Felicity Chapman Date: Thu, 24 Oct 2024 09:27:32 +0100 Subject: [PATCH 2/2] Create Copilot group on Home page without affecting GHES users: #2 (#52832) Co-authored-by: Rachael Sewell --- content/index.md | 22 +++++++++++++------ .../components/ProductSelectionCard.tsx | 5 +++++ 2 files changed, 20 insertions(+), 7 deletions(-) diff --git a/content/index.md b/content/index.md index ab878f7e4ef1..855610b01ec8 100644 --- 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,6 +135,13 @@ 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: @@ -135,14 +149,8 @@ childGroups: - 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/src/landings/components/ProductSelectionCard.tsx b/src/landings/components/ProductSelectionCard.tsx index 6ba80ceff7cd..d60e55ae37b7 100644 --- 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', }