From 3bfef1656ad5cc3e5a12a4e39a69f346f83cc115 Mon Sep 17 00:00:00 2001 From: Hanbyul Jo Date: Tue, 7 Jan 2025 09:17:53 -0500 Subject: [PATCH] Link configuration repo --- docs/development/RELEASE.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/development/RELEASE.md b/docs/development/RELEASE.md index ea9b0ce20..d46c9b625 100644 --- a/docs/development/RELEASE.md +++ b/docs/development/RELEASE.md @@ -14,7 +14,7 @@ The automated process handles - Creating Git tag using the version number - Creating a commit bumping the version number up in `package.json` - Creating GitHub Release -- Creating VEDA instance preview using VEDA UI version (When the release is made from `main` branch) +- Creating [VEDA configuration instance](https://github.com/nasa-impact/veda-config) preview using VEDA UI version (When the release is made from `main` branch) ### GitHub Action Integration @@ -26,7 +26,7 @@ If you are a contributor, you can trigger a release action through the Actions t #### Instance Build -Upon triggering, the GitHub Action builds the Configuration (veda-config) instances using the specified release. It will create a Pull Request, as shown below, on veda-config, building a preview using the released UI. +Upon triggering, the GitHub Action builds the [Configuration (veda-config) instance](https://github.com/nasa-impact/veda-config) using the specified release. It will create a Pull Request, as shown below, on veda-config, building a preview using the released UI. ![Screenshot of generated PR ](../media/preview-pr.png)