From dd5482a899c2228dd6bc1278faf99dc5c8da2f66 Mon Sep 17 00:00:00 2001
From: Arun Chapagain <99020948+ArunChapagain@users.noreply.github.com>
Date: Thu, 20 Nov 2025 18:18:13 +0545
Subject: [PATCH] docs: Update developing extension docs for updating specific
 submodule (#42548)

Release Notes:

- N/A
---
 docs/src/extensions/developing-extensions.md | 12 ++++++++++++
 1 file changed, 12 insertions(+)

diff --git a/docs/src/extensions/developing-extensions.md b/docs/src/extensions/developing-extensions.md
index e86533c0c0c357147d291894167b149d99af5d1d..539cbe3d3044afe30b6ced4f3ceb61f537ebde75 100644
--- a/docs/src/extensions/developing-extensions.md
+++ b/docs/src/extensions/developing-extensions.md
@@ -109,6 +109,18 @@ git submodule init
 git submodule update
 ```
 
+## Update Your Extension
+
+When developing/updating your extension, you will likely need to update its content from its submodule in the extensions repository.
+To quickly fetch the latest code for only specific extension (and avoid updating all others), use the specific path:
+
+```sh
+# From the root of the repository:
+git submodule update --remote extensions/your-extension-name
+```
+
+> Note: If you need to update all submodules (e.g., if multiple extensions have changed, or for a full clean build), you can run `git submodule update` without a path, but this will take longer.
+
 ## Extension License Requirements
 
 As of October 1st, 2025, extension repositories must include a license.