From 25df4aa5abd656af1eb58f4208dd0db95626c857 Mon Sep 17 00:00:00 2001
From: Jilles Soeters <jilles@cloudflare.com>
Date: Wed, 8 Oct 2025 07:32:40 -0500
Subject: [PATCH 1/2] [Zero Trust] Update GitHud identity

---
 .../cloudflare-one/identity/idp-integration/github.mdx   | 9 ++++++++-
 1 file changed, 8 insertions(+), 1 deletion(-)

diff --git a/src/content/docs/cloudflare-one/identity/idp-integration/github.mdx b/src/content/docs/cloudflare-one/identity/idp-integration/github.mdx
index 7452d1bdcbed85..f499d1fab0e1b1 100644
--- a/src/content/docs/cloudflare-one/identity/idp-integration/github.mdx
+++ b/src/content/docs/cloudflare-one/identity/idp-integration/github.mdx
@@ -3,6 +3,8 @@ pcx_content_type: how-to
 title: GitHub
 ---
 
+import { Aside } from '@astrojs/starlight/components';
+
 Cloudflare Zero Trust allows your team to connect to your applications using their GitHub login. You do not need to have a GitHub organization to use the integration.
 
 ## Set up GitHub Access
@@ -48,6 +50,11 @@ To configure GitHub access in both GitHub and Cloudflare Zero Trust:
 To test that your connection is working, go to [Zero Trust](https://one.dash.cloudflare.com) > **Authentication** > **Login methods** and select **Test** next to your GitHub login method.
 If you have GitHub two-factor authentication enabled, you will need to first login to GitHub directly and return to Access.
 
+
+<Aside title="Troubleshooting Organization Policies">
+When using a GitHub organization policy, if a user joins the required organization *after* a failed login attempt, they will remain blocked. To fix this, they must **revoke the application's access in their GitHub settings** and log in again to update their permissions.
+</Aside>
+
 ## Example API Configuration
 
 ```json
@@ -59,4 +66,4 @@ If you have GitHub two-factor authentication enabled, you will need to first log
 	"type": "github",
 	"name": "my example idp"
 }
-```
+```
\ No newline at end of file

From fa85f15aaf320b67edec4a75ac52df94c6274610 Mon Sep 17 00:00:00 2001
From: Jilles Soeters <jilles@cloudflare.com>
Date: Wed, 8 Oct 2025 07:38:18 -0500
Subject: [PATCH 2/2] Use styleguide aside

---
 .../docs/cloudflare-one/identity/idp-integration/github.mdx | 6 ++----
 1 file changed, 2 insertions(+), 4 deletions(-)

diff --git a/src/content/docs/cloudflare-one/identity/idp-integration/github.mdx b/src/content/docs/cloudflare-one/identity/idp-integration/github.mdx
index f499d1fab0e1b1..e238b33b1a68a4 100644
--- a/src/content/docs/cloudflare-one/identity/idp-integration/github.mdx
+++ b/src/content/docs/cloudflare-one/identity/idp-integration/github.mdx
@@ -3,8 +3,6 @@ pcx_content_type: how-to
 title: GitHub
 ---
 
-import { Aside } from '@astrojs/starlight/components';
-
 Cloudflare Zero Trust allows your team to connect to your applications using their GitHub login. You do not need to have a GitHub organization to use the integration.
 
 ## Set up GitHub Access
@@ -51,9 +49,9 @@ To test that your connection is working, go to [Zero Trust](https://one.dash.clo
 If you have GitHub two-factor authentication enabled, you will need to first login to GitHub directly and return to Access.
 
 
-<Aside title="Troubleshooting Organization Policies">
+:::note[Troubleshooting Organization Policies]
 When using a GitHub organization policy, if a user joins the required organization *after* a failed login attempt, they will remain blocked. To fix this, they must **revoke the application's access in their GitHub settings** and log in again to update their permissions.
-</Aside>
+:::
 
 ## Example API Configuration