summaryrefslogtreecommitdiff
path: root/CONTRIBUTING.md
diff options
context:
space:
mode:
authorcjihrig <cjihrig@gmail.com>2014-10-09 22:17:42 -0400
committercjihrig <cjihrig@gmail.com>2014-10-10 12:57:50 -0400
commit051dc546d6c155de047cbbc07c44e8f905a7a332 (patch)
treed22432b6b33746bee70d0aeee48173b6f4dde01d /CONTRIBUTING.md
parentf60abb0ced54f5ba08d324e62ad3fbb306ba37f7 (diff)
downloadnode-new-051dc546d6c155de047cbbc07c44e8f905a7a332.tar.gz
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 <info@bnoordhuis.nl> Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Diffstat (limited to 'CONTRIBUTING.md')
-rw-r--r--CONTRIBUTING.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 62af881fae..6e43d0cc28 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 <your-email>` 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.