From a9d67907ae2e1f1b8ab30b5ecb5b554462f0894a Mon Sep 17 00:00:00 2001 From: lakshmimsft Date: Fri, 20 Sep 2024 10:05:02 -0700 Subject: [PATCH] upd with link --- docs/contributing/contributing-recipes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/contributing/contributing-recipes.md b/docs/contributing/contributing-recipes.md index f7d9d51..2a8d506 100644 --- a/docs/contributing/contributing-recipes.md +++ b/docs/contributing/contributing-recipes.md @@ -108,7 +108,7 @@ After you have tested the recipe in an application, you can follow the steps bel 1. Make sure there's an issue (bug or feature) raised, which sets the expectations for the contribution you are about to make. 1. Fork the repository and create a new branch 1. Add the recipe to the relevant directory following the [repository structure](../../README.md#repository-structure) -1. Update the README.md with the new recipe +1. Update the [README.md](https://github.com/radius-project/recipes/blob/main/local-dev/README.md) with the new recipe 1. Commit and open a PR 1. Wait for the CI process to finish and make sure all checks are green 1. A maintainer of the repo will be assigned, and you can expect a review within a few days