From ae1061990dd5f5244c2ac622c998f1e7c11d9902 Mon Sep 17 00:00:00 2001 From: Ravi Srinivasan Date: Thu, 14 Nov 2024 06:21:56 +0530 Subject: [PATCH] minor typo fix --- modules/ROOT/pages/custom-plugin-registry.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/ROOT/pages/custom-plugin-registry.adoc b/modules/ROOT/pages/custom-plugin-registry.adoc index 42fc280..ea58244 100644 --- a/modules/ROOT/pages/custom-plugin-registry.adoc +++ b/modules/ROOT/pages/custom-plugin-registry.adoc @@ -180,7 +180,7 @@ devspaces-587dc9fbdd-vzr75 1/1 Running *plugin-registry-69c69ff5b7-2g4lg* 1/1 Running_ ---- -. Launch a new workspace using the Git repository URL https://github.com/rsriniva/devspaces-plugins-demo[window=_blank], and check the available extensions in the `Extensions` view of the workspace IDE. You should see the two new plugins you added to the custom embedded plugin registry. After the workspace is started, the two plugins should be automatically installed since the repository containers a `.vscode` folder with a recommendations JSON file with the list of plugins to install automatically. +. Launch a new workspace using the Git repository URL https://github.com/rsriniva/devspaces-plugins-demo[window=_blank], and check the available extensions in the `Extensions` view of the workspace IDE. You should see the two new plugins you added to the custom embedded plugin registry. After the workspace is started, the two plugins should be automatically installed since the repository contains a `.vscode` folder with a recommendations JSON file with the list of plugins to install automatically. . Search the public Open VSX registry for plugins that are NOT in the `openvsx-sync.json` file, and verify that only plugins added to the JSON file before the custom build show up in the workspace.