From 3eee2ead899dfff76c46a181b872a6ca6f455eb3 Mon Sep 17 00:00:00 2001
From: Eric Williams <ericwill@users.noreply.github.com>
Date: Mon, 17 Feb 2020 04:30:15 -0500
Subject: [PATCH] Clarify process for adding a VS Code extension to Che (#1074)

Improve the docs a bit so that it's clear that a meta.yaml file
can be hosted on GitHub, and not just a self-hosted registry link.

See eclipse/che#15982

Signed-off-by: Eric Williams <ericwill@redhat.com>
---
 ...de-extension-using-the-workspace-configuration.adoc | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/src/main/pages/che-7/end-user-guide/proc_adding-the-vs-code-extension-using-the-workspace-configuration.adoc b/src/main/pages/che-7/end-user-guide/proc_adding-the-vs-code-extension-using-the-workspace-configuration.adoc
index baafe590d2..8e5f636d1d 100644
--- a/src/main/pages/che-7/end-user-guide/proc_adding-the-vs-code-extension-using-the-workspace-configuration.adoc
+++ b/src/main/pages/che-7/end-user-guide/proc_adding-the-vs-code-extension-using-the-workspace-configuration.adoc
@@ -25,5 +25,15 @@ To add a VS Code extension using the workspace configuration:
 <1> Link to the `meta.yaml` file in your registry, for example, `https://my-plug-in-registry/v3/plugins/__<publisher>__/__<plug-inName>__/__<plug-inVersion>__/meta.yaml`
 +
 {prod-short} automatically adds the other fields to the new component.
++
+Alternatively, you can link to a `meta.yaml` file hosted on GitHub, via the reference field.
++
+[source,yaml,subs="+quotes"]
+----
+ - type: chePlugin
+   reference:              <1>
+----
+<1> `https://raw.githubusercontent.com/__<username>__/__<registryRepository>__/v3/plugins/__<publisher>__/__<plug-inName>__/__<plug-inVersion>__/meta.yaml`
++
 
 . Restart the workspace for the changes to take effect.