diff options
author | Xavier Noria <fxn@hashref.com> | 2011-02-15 22:17:25 +0100 |
---|---|---|
committer | Xavier Noria <fxn@hashref.com> | 2011-02-15 22:17:25 +0100 |
commit | 5444ed56ab38a742b3ddf6612eadd8cf50d8d517 (patch) | |
tree | fa30730437a25b6b3a1d990e40e5e6b0d428bc6f /railties/guides/source | |
parent | f4ddb4da89906e2339eefcb835e2af4673218b30 (diff) | |
download | rails-5444ed56ab38a742b3ddf6612eadd8cf50d8d517.tar.gz rails-5444ed56ab38a742b3ddf6612eadd8cf50d8d517.tar.bz2 rails-5444ed56ab38a742b3ddf6612eadd8cf50d8d517.zip |
Revert "Fix error: docrails is a fork, not a branch."
Reason: Calling docrails a "branch" is fine, no need to change the terminology. It is a remote in my machine, and it has been called branch since the very beginning: http://weblog.rubyonrails.org/2008/5/2/help-improve-rails-documentation-on-git-branch
This reverts commit 35a266edfd9ac0f3afe7f7f13c2dcf29cb4b651f.
Diffstat (limited to 'railties/guides/source')
-rw-r--r-- | railties/guides/source/contributing_to_ruby_on_rails.textile | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/railties/guides/source/contributing_to_ruby_on_rails.textile b/railties/guides/source/contributing_to_ruby_on_rails.textile index 830b055359..4f51c0f859 100644 --- a/railties/guides/source/contributing_to_ruby_on_rails.textile +++ b/railties/guides/source/contributing_to_ruby_on_rails.textile @@ -253,7 +253,7 @@ h3. Contributing to the Rails Documentation Ruby on Rails has two main sets of documentation: The guides help you to learn Ruby on Rails, and the API is a reference. -You can create a ticket in Lighthouse to fix or expand documentation. However, if you're confident about your changes you can push them yourself directly via "docrails":http://github.com/lifo/docrails/tree/master. docrails is a fork of the Rails repository with an *open commit policy* and public write access. Commits to docrails are still reviewed, but that happens after they are pushed. docrails is merged with master regularly, so you are effectively editing the Ruby on Rails documentation. +You can create a ticket in Lighthouse to fix or expand documentation. However, if you're confident about your changes you can push them yourself directly via "docrails":http://github.com/lifo/docrails/tree/master. docrails is a branch with an *open commit policy* and public write access. Commits to docrails are still reviewed, but that happens after they are pushed. docrails is merged with master regularly, so you are effectively editing the Ruby on Rails documentation. When working with documentation, please take into account the "API Documentation Guidelines":api_documentation_guidelines.html and the "Ruby on Rails Guides Guidelines":ruby_on_rails_guides_guidelines.html. |