docs: Improve documentation for updating an extension (#44475)

Finn Evers created 2 weeks ago

Release Notes:

- N/A

Change summary

docs/src/extensions/developing-extensions.md | 22 +++++++++-------------
1 file changed, 9 insertions(+), 13 deletions(-)

Detailed changes

docs/src/extensions/developing-extensions.md

@@ -109,18 +109,6 @@ 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.
@@ -177,7 +165,15 @@ To update an extension, open a PR to [the `zed-industries/extensions` repo](http
 
 In your PR do the following:
 
-1. Update the extension's submodule to the commit of the new version.
+1. Update the extension's submodule to the commit of the new version. For this, you can run
+
+```sh
+# From the root of the repository:
+git submodule update --remote extensions/your-extension-name
+```
+
+to update your extension to the latest commit available in your remote repository.
+
 2. Update the `version` field for the extension in `extensions.toml`
    - Make sure the `version` matches the one set in `extension.toml` at the particular commit.