From 051dc546d6c155de047cbbc07c44e8f905a7a332 Mon Sep 17 00:00:00 2001 From: cjihrig Date: Thu, 9 Oct 2014 22:17:42 -0400 Subject: [PATCH] node: update links in CONTRIBUTING.md Two links still point to the Joyent repo. This commit updates the links to point to node-forward. PR-URL: https://github.com/node-forward/node/pull/11 Reviewed-By: Ben Noordhuis Reviewed-By: Colin Ihrig --- CONTRIBUTING.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 62af881fae8bbb..6e43d0cc289f44 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -147,7 +147,7 @@ feature branch. Post a comment in the pull request afterwards; GitHub does not send out notifications when you add commits. -[stability index page]: https://github.com/joyent/node/blob/master/doc/api/documentation.markdown +[stability index page]: https://github.com/node-forward/node/blob/master/doc/api/documentation.markdown [issue tracker]: https://github.com/node-forward/node/issues [node.js mailing list]: http://groups.google.com/group/nodejs [IRC]: http://webchat.freenode.net/?channels=node.js @@ -160,7 +160,7 @@ rules to follow. - Always include the `Reviewed-by: You Name ` in the commit message. - In commit messages also include `Fixes:` that either includes the - **full url** (e.g. `https://github.com/joyent/node/issues/...`), and/or + **full url** (e.g. `https://github.com/node-forward/node/issues/...`), and/or the hash and commit message if the commit fixes a bug in a previous commit. - PR's should include their full `PR-URL:` so it's easy to trace a commit back to the conversation that lead up to that change.