From 439617b9504a6a9bdd9f1f631df073e88c75752a Mon Sep 17 00:00:00 2001
From: "dependabot[bot]" <49699333+dependabot[bot]@users.noreply.github.com>
Date: Mon, 6 May 2024 12:57:11 +0000
Subject: [PATCH 1/2] Bump html-entities from 2.4.0 to 2.5.2 (#50454)

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
---
 package-lock.json | 8 ++++----
 package.json      | 2 +-
 2 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/package-lock.json b/package-lock.json
index 3ccd9371f936..c4e3f7b64120 100644
--- a/package-lock.json
+++ b/package-lock.json
@@ -48,7 +48,7 @@
         "highlight.js": "11.9.0",
         "highlightjs-curl": "^1.3.0",
         "hot-shots": "^10.0.0",
-        "html-entities": "^2.4.0",
+        "html-entities": "^2.5.2",
         "http-proxy-middleware": "3.0.0",
         "imurmurhash": "^0.1.4",
         "is-svg": "5.0.0",
@@ -7852,9 +7852,9 @@
       }
     },
     "node_modules/html-entities": {
-      "version": "2.4.0",
-      "resolved": "https://registry.npmjs.org/html-entities/-/html-entities-2.4.0.tgz",
-      "integrity": "sha512-igBTJcNNNhvZFRtm8uA6xMY6xYleeDwn3PeBCkDz7tHttv4F2hsDI2aPgNERWzvRcNYHNT3ymRaQzllmXj4YsQ==",
+      "version": "2.5.2",
+      "resolved": "https://registry.npmjs.org/html-entities/-/html-entities-2.5.2.tgz",
+      "integrity": "sha512-K//PSRMQk4FZ78Kyau+mZurHn3FH0Vwr+H36eE0rPbeYkRRi9YxceYPhuN60UwWorxyKHhqoAJl2OFKa4BVtaA==",
       "funding": [
         {
           "type": "github",
diff --git a/package.json b/package.json
index d75b9f814841..83592f170a04 100644
--- a/package.json
+++ b/package.json
@@ -234,7 +234,7 @@
     "highlight.js": "11.9.0",
     "highlightjs-curl": "^1.3.0",
     "hot-shots": "^10.0.0",
-    "html-entities": "^2.4.0",
+    "html-entities": "^2.5.2",
     "http-proxy-middleware": "3.0.0",
     "imurmurhash": "^0.1.4",
     "is-svg": "5.0.0",

From 7355676b1b0bbb8c2b56a30b55acf752afcde12c Mon Sep 17 00:00:00 2001
From: Kynan Ware <47394200+BagToad@users.noreply.github.com>
Date: Mon, 6 May 2024 07:06:22 -0600
Subject: [PATCH 2/2] Clarify `.github` repository visibility requirement for
 starter workflows (#50421)

Co-authored-by: Thomas Cole <51364971+thomasjohncole@users.noreply.github.com>
---
 .../creating-starter-workflows-for-your-organization.md    | 7 +++++--
 1 file changed, 5 insertions(+), 2 deletions(-)

diff --git a/content/actions/using-workflows/creating-starter-workflows-for-your-organization.md b/content/actions/using-workflows/creating-starter-workflows-for-your-organization.md
index cb1bf4d501c6..281b3d6a64fd 100644
--- a/content/actions/using-workflows/creating-starter-workflows-for-your-organization.md
+++ b/content/actions/using-workflows/creating-starter-workflows-for-your-organization.md
@@ -24,9 +24,12 @@ topics:
 
 {% data reusables.actions.starter-workflow-categories %}
 
+> [!NOTE]
+> Because starter workflows require a public `.github` repository, they are not available for {% data variables.product.prodname_emus %}.
+
 ## Creating a starter workflow
 
-Starter workflows can be created by users with write access to the organization's `.github` repository. These can then be used by organization members who have permission to create workflows.
+Starter workflows can be created by users with write access to the organization's _public_ `.github` repository. These can then be used by organization members who have permission to create workflows.
 
 {% ifversion fpt %}
 Starter workflows created by users can only be used to create workflows in public repositories. Organizations using {% data variables.product.prodname_ghe_cloud %} can also use starter workflows to create workflows in private repositories. For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/actions/using-workflows/creating-starter-workflows-for-your-organization).
@@ -40,7 +43,7 @@ Starter workflows created by users can only be used to create workflows in publi
 
 This procedure demonstrates how to create a starter workflow and metadata file. The metadata file describes how the starter workflows will be presented to users when they are creating a new workflow.
 
-1. If it doesn't already exist, create a new public repository named `.github` in your organization.
+1. If it doesn't already exist, create a new _public_ repository named `.github` in your organization.
 1. Create a directory named `workflow-templates`.
 1. Create your new workflow file inside the `workflow-templates` directory.