diff options
| author | Scott Freeman <gsfreema@gmail.com> | 2017-06-28 11:39:48 -0400 |
|---|---|---|
| committer | Scott Freeman <gsfreema@gmail.com> | 2017-06-28 13:25:52 -0400 |
| commit | 116178885631e4c6bb87d4dcf2f5e6d82e77850b (patch) | |
| tree | 1468840d0abfe4856aebfb38db2e61918cb61439 /Documentation/project-docs | |
| parent | 217ab30d021f27be6fe4f35126a88e592366acbf (diff) | |
| download | coreclr-116178885631e4c6bb87d4dcf2f5e6d82e77850b.tar.gz coreclr-116178885631e4c6bb87d4dcf2f5e6d82e77850b.tar.bz2 coreclr-116178885631e4c6bb87d4dcf2f5e6d82e77850b.zip | |
Fix contributing workflow commit message link
A recent change moved the Commit Messages section to a different
markdown file. This change fixes that link, and provides relative
paths for links where appropiate. This keeps people in their own
fork of the repo when browsing on github.
Diffstat (limited to 'Documentation/project-docs')
| -rw-r--r-- | Documentation/project-docs/contributing-workflow.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/project-docs/contributing-workflow.md b/Documentation/project-docs/contributing-workflow.md index f09c7cc36d..20ce15f4e3 100644 --- a/Documentation/project-docs/contributing-workflow.md +++ b/Documentation/project-docs/contributing-workflow.md @@ -10,7 +10,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/master/CODE_OWNERS.TXT) to find relevant maintainers and @ mention them to ask for feedback on your issue. + - Use [CODE_OWNERS.TXT](../../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. @@ -19,7 +19,7 @@ We use and recommend the following workflow: - Name the branch so that it clearly communicates your intentions, such as issue-123 or githubhandle-issue. - Branches are useful since they isolate your changes from incoming changes from upstream. They also enable you to create multiple PRs from the same fork. 4. Make and commit your changes. - - Please follow our [Commit Messages](https://github.com/dotnet/coreclr/blob/master/Documentation/project-docs/contributing-workflow.md#commit-messages) guidance. + - Please follow our [Commit Messages](contributing.md#commit-messages) guidance. 5. Add new tests corresponding to your change, if applicable. 6. Build the repository with your changes. - Make sure that the builds are clean. |