about summary refs log tree commit diff
diff options
context:
space:
mode:
authorbors <bors@rust-lang.org>2017-08-12 14:24:40 +0000
committerbors <bors@rust-lang.org>2017-08-12 14:24:40 +0000
commit045ca8b43b86f6a1671a59cc43cf535eebcb074e (patch)
tree35ba9199393dec14414f743d248bd7bd480d27c1
parent456493353867832170045cb063aebf22fa8a7201 (diff)
parenta746129bdb50186994c6f62769ff043bb58f6fd7 (diff)
downloadrust-045ca8b43b86f6a1671a59cc43cf535eebcb074e.tar.gz
rust-045ca8b43b86f6a1671a59cc43cf535eebcb074e.zip
Auto merge of #43823 - tchajed:fix-pr-link, r=frewsxcv
Update GitHub pull request documentation link

It looks like the GitHub documentation has been re-organized so that the "fork and pull" model isn't explained alongside the PR process in one convenient link any more.
-rw-r--r--CONTRIBUTING.md9
1 files changed, 6 insertions, 3 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 04b6fea75a7..a8ab9ff48b4 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -237,10 +237,13 @@ Some common invocations of `x.py` are:
 ## Pull Requests
 
 Pull requests are the primary mechanism we use to change Rust. GitHub itself
-has some [great documentation][pull-requests] on using the Pull Request
-feature. We use the 'fork and pull' model described there.
+has some [great documentation][pull-requests] on using the Pull Request feature.
+We use the "fork and pull" model [described here][development-models], where
+contributors push changes to their personal fork and create pull requests to
+bring those changes into the source repository.
 
-[pull-requests]: https://help.github.com/articles/using-pull-requests/
+[pull-requests]: https://help.github.com/articles/about-pull-requests/
+[development-models]: https://help.github.com/articles/about-collaborative-development-models/
 
 Please make pull requests against the `master` branch.