From 051fa06c7c447ab9f01d14ca0a8219f318b59468 Mon Sep 17 00:00:00 2001 From: "Joseph T. Lyons" Date: Tue, 17 Jun 2025 16:31:39 -0400 Subject: [PATCH] Add docs for cloning extensions repository (#32897) Release Notes: - N/A --------- Co-authored-by: Peter Tripp --- docs/src/extensions/developing-extensions.md | 18 ++++++++++++++++-- 1 file changed, 16 insertions(+), 2 deletions(-) diff --git a/docs/src/extensions/developing-extensions.md b/docs/src/extensions/developing-extensions.md index e18174e95d..2b8aaef3ec 100644 --- a/docs/src/extensions/developing-extensions.md +++ b/docs/src/extensions/developing-extensions.md @@ -89,12 +89,26 @@ impl zed::Extension for MyExtension { zed::register_extension!(MyExtension); ``` +## Forking and cloning the repo + +1. Fork the repo + +> Note: It is very helpful if you fork the `zed-industries/extensions` repo to a personal GitHub account instead of a GitHub organization, as this allows Zed staff to push any needed changes to your PR to expedite the publishing process. + +2. Clone the repo to your local machine + +```sh +# Substitute the url of your fork here: +# git clone https://github.com/zed-industries/extensions +cd extensions +git submodule init +git submodule update +``` + ## Publishing your extension To publish an extension, open a PR to [the `zed-industries/extensions` repo](https://github.com/zed-industries/extensions). -> Note: It is very helpful if you fork the `zed-industries/extensions` repo to a personal GitHub account instead of a GitHub organization, as this allows Zed staff to push any needed changes to your PR to expedite the publishing process. - In your PR, do the following: 1. Add your extension as a Git submodule within the `extensions/` directory