diff options
author | Dan Moseley <danmose@microsoft.com> | 2017-01-05 08:52:34 -0800 |
---|---|---|
committer | GitHub <noreply@github.com> | 2017-01-05 08:52:34 -0800 |
commit | 25dc0b6b7d9ee40a9d64a570ada8821d2e8f0f76 (patch) | |
tree | d28332dcdc9bb8c6cf1c41856af252cb7555a17a /Documentation | |
parent | f66ba4a14a5e729778d66ea6cc1409f0e8b4a5b0 (diff) | |
download | coreclr-25dc0b6b7d9ee40a9d64a570ada8821d2e8f0f76.tar.gz coreclr-25dc0b6b7d9ee40a9d64a570ada8821d2e8f0f76.tar.bz2 coreclr-25dc0b6b7d9ee40a9d64a570ada8821d2e8f0f76.zip |
fix link
Fix https://github.com/dotnet/coreclr/issues/8816
Diffstat (limited to 'Documentation')
-rw-r--r-- | Documentation/project-docs/contributing-workflow.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/project-docs/contributing-workflow.md b/Documentation/project-docs/contributing-workflow.md index 5c91a49bae..70423e573b 100644 --- a/Documentation/project-docs/contributing-workflow.md +++ b/Documentation/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. |