From 64ede919009915fc34605d83aa0c7860d1a9c4cd Mon Sep 17 00:00:00 2001
From: Erik Engervall <erik.engervall@gmail.com>
Date: Mon, 12 Apr 2021 18:39:25 +0200
Subject: [PATCH] Add 'Usage' to docs

Signed-off-by: Erik Engervall <erik.engervall@gmail.com>
---
 plugins/release-manager-as-a-service/README.md | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/plugins/release-manager-as-a-service/README.md b/plugins/release-manager-as-a-service/README.md
index cdd50d35c6..ffb39f2c8f 100644
--- a/plugins/release-manager-as-a-service/README.md
+++ b/plugins/release-manager-as-a-service/README.md
@@ -43,3 +43,7 @@ Looking at the flow above, a common release lifecycle could be:
   - Your CI
     1. Detects the new tag by matching the git reference `refs/tags/version-.*`
     1. Builds and deploys to production for testing
+
+## Usage
+
+The plugin exports a single full-page extension `ReleaseManagerAsAServicePage`, which one can add to an app like a usual top-level tool on a dedicated route.