From d28970700a3c0e77dfdd5194d8a99263a77cadd7 Mon Sep 17 00:00:00 2001 From: Doug Davis Date: Thu, 7 Apr 2022 12:30:27 +0000 Subject: [PATCH] Add link to the dev docs I may have missed it but I couldn't find a way to go from the main README (https://github.com/dapr/dapr) to the dev docs. Signed-off-by: Doug Davis --- daprdocs/content/en/contributing/contributing-overview.md | 1 + 1 file changed, 1 insertion(+) diff --git a/daprdocs/content/en/contributing/contributing-overview.md b/daprdocs/content/en/contributing/contributing-overview.md index 69bb68c2f..eec7290e8 100644 --- a/daprdocs/content/en/contributing/contributing-overview.md +++ b/daprdocs/content/en/contributing/contributing-overview.md @@ -51,6 +51,7 @@ All contributions come through pull requests. To submit a proposed change, follo 1. Make sure there's an issue (bug or proposal) raised, which sets the expectations for the contribution you are about to make. 1. Fork the relevant repo and create a new branch - Some Dapr repos support [Codespaces]({{< ref codespaces.md >}}) to provide an instant environment for you to build and test your changes. + - See the [Developing Dapr docs](https://github.com/dapr/dapr/blob/master/docs/development/developing-dapr.md) for more information about setting up a Dapr development environment. 1. Create your change - Code changes require tests 1. Update relevant documentation for the change