summaryrefslogtreecommitdiff
path: root/Documentation/project-docs
diff options
context:
space:
mode:
authorBenjamin Hodgson <benjamin.hodgson@huddle.com>2015-09-04 11:57:44 +0100
committerBenjamin Hodgson <benjamin.hodgson@huddle.com>2015-09-04 11:57:44 +0100
commit01959412e9d2e270bfa54b256072b102a6c660ac (patch)
tree313cc34775c1e67269a97ee427821623a8405ad5 /Documentation/project-docs
parent1165038551b7ca20f230d867dc5fd2357ede14fe (diff)
downloadcoreclr-01959412e9d2e270bfa54b256072b102a6c660ac.tar.gz
coreclr-01959412e9d2e270bfa54b256072b102a6c660ac.tar.bz2
coreclr-01959412e9d2e270bfa54b256072b102a6c660ac.zip
Fix link to API review process documentation
Diffstat (limited to 'Documentation/project-docs')
-rw-r--r--Documentation/project-docs/contributing-workflow.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/project-docs/contributing-workflow.md b/Documentation/project-docs/contributing-workflow.md
index aabc6f5c00..21c7d2e82a 100644
--- a/Documentation/project-docs/contributing-workflow.md
+++ b/Documentation/project-docs/contributing-workflow.md
@@ -86,7 +86,7 @@ We use and recommend the following workflow:
- You can skip this step for trivial changes.
- Reuse an existing issue on the topic, if there is one.
- 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/api-review-process.md).
+ - 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. Create a personal fork of the repository on GitHub (if you don't already have one).
3. Create a branch off of master (`git checkout -b mybranch`).