From e1279b5c305db69502914b2cdefc7ce63c11581e Mon Sep 17 00:00:00 2001 From: Dan Moseley Date: Thu, 5 Jan 2017 08:52:34 -0800 Subject: [PATCH] fix link Fix https://github.com/dotnet/coreclr/issues/8816 Commit migrated from https://github.com/dotnet/coreclr/commit/25dc0b6b7d9ee40a9d64a570ada8821d2e8f0f76 --- docs/coreclr/project-docs/contributing-workflow.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/coreclr/project-docs/contributing-workflow.md b/docs/coreclr/project-docs/contributing-workflow.md index 5c91a49..70423e5 100644 --- a/docs/coreclr/project-docs/contributing-workflow.md +++ b/docs/coreclr/project-docs/contributing-workflow.md @@ -85,7 +85,7 @@ We use and recommend the following workflow: 1. Create an issue for your work. - You can skip this step for trivial changes. - Reuse an existing issue on the topic, if there is one. - - Use [CODE_OWNERS.TXT](https://github.com/dotnet/coreclr/blob/CODE_OWNERS.TXT) to find relevant maintainers and @ mention them to ask for feedback on your issue. + - Use [CODE_OWNERS.TXT](https://github.com/dotnet/coreclr/blob/master/CODE_OWNERS.TXT) to find relevant maintainers and @ mention them to ask for feedback on your issue. - Get agreement from the team and the community that your proposed change is a good one. - If your change adds a new API, follow the [API Review Process](https://github.com/dotnet/corefx/blob/master/Documentation/project-docs/api-review-process.md). - Clearly state that you are going to take on implementing it, if that's the case. You can request that the issue be assigned to you. Note: The issue filer and the implementer don't have to be the same person. -- 2.7.4