aboutsummaryrefslogtreecommitdiffstats
path: root/guides/source/contributing_to_ruby_on_rails.md
Commit message (Collapse)AuthorAgeFilesLines
* .git added to https repo urlsVishnu Ks2016-02-021-5/+5
|
* git protocol replaced with httpsVishnu Ks2016-02-021-5/+5
|
* typo fix [ci skip] Prayag Verma2016-01-311-1/+1
| | | Spelling mistake - direcotry > directory
* remove legacy mysql from guides to match #22715Scott Bronson2016-01-091-1/+0
|
* fix links to code of conduct [ci skip]yuuji.yaginuma2015-12-111-1/+1
| | | | CoC text has been moved to the Rails website in 90bcb6d
* [ci skip] Add `Translating Rails Guides` to contributing_to_ruby_on_railsyui-knk2015-11-231-0/+36
| | | | | | | Docrails is private now (6cb1b6724c313c608cf4063fc22886faa19df9be), anyone who does not have access right to docrails can't read "Translating Rails Guides" in wiki of docrails. To prevent someone from giving up to translate, publish them on Rails Guide.
* Remove links to docrailsRafael Mendonça França2015-11-051-2/+2
| | | | docrails is a private repository now to avoid pull requests to it.
* Fix pluralization in docs [ci skip]Scott González2015-10-071-1/+1
|
* [ci skip] Add `:` before code blocks.yui-knk2015-09-251-1/+1
|
* typo fix [ci skip]amitkumarsuroliya2015-09-011-1/+1
| | | sub-project's should be sub-projects' at all places
* Add code of conduct to README.md and to contributing guide [ci skip]maclover72015-08-181-0/+3
|
* [ci skip] Add `bundle exec` to test run commandyui-knk2015-07-171-1/+1
|
* the key is that the behavior is incorrect [ci skip]Tony Miller2015-07-111-1/+1
|
* saying that "behaviour" "behaves" is kind of awkward, how about "works"Tony Miller2015-07-101-1/+1
|
* [ci skip] change sentence about reporting bugs in contributing guideTony Miller2015-07-101-1/+1
| | | | | | I think I know what this sentence is trying to say, but the sentence didn't really make sense, bugs don't fix things! How about this take on it? :sweat_smile:
* [ci skip] Add `bundle exec` to Running a Single Testyui-knk2015-07-081-1/+1
|
* Maintaining consistency in wordings [ci skip]Rohan Daxini2015-06-271-1/+1
| | | "reproduce" word is better suited then "replicate" as its also used at other places in this same document having same context. It will then be consistent across document.
* Fixed the grammatical mistake in the sentence [ci skip]Rohan Daxini2015-05-251-1/+1
|
* Reword sentences in contributing docs for clarity.Daniel Levenson2015-05-231-3/+3
| | | | | | | | [skip ci] - removes use "squash" where it doesn't apply to git - "is a help" -> "helps" - "if your comment simply says" -> "... simply reads"
* Reword a sentence about GH Issues in contributing guide.Daniel Levenson2015-05-231-1/+1
| | | | | | | | | [skip ci] "Everyone's Issues" read pretty weird to me, specifically the use of capitalization. I changed the link text to be "issue list", which seems to better "go with the flow", IMHO.
* updated squash docs-section [ci skip]Gourav Tiwari2015-05-191-2/+1
| | | | | I happen to squash my couple of commits and when followed steps from guide, I observed that I have to give a commit id after which I want to squash. If I don't provide one it picks last 3 commits, which might not include my commits to squash. Refer: http://stackoverflow.com/questions/5189560/squash-my-last-x-commits-together-using-git
* fixes some words missingTravis Yoder2015-05-041-1/+1
|
* Merge pull request #19779 from ↵Zachary Scott2015-04-211-13/+20
|\ | | | | | | | | jonatack/improve-contributing-to-ruby-on-rails-guide Improve the Contributing to Rails Guide [skip ci]
| * Improve the Contributing to Rails Guide [skip ci]Jon Atack2015-04-161-13/+20
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | First commit: This PR improves the "4.12 Commit Your Changes" section of the Contributing to Ruby on Rails Guide: - Fix formatting of the commit message example - Improve readability and clarity - Fix grammar - Wrap lines See the before and after images below in this PR. ----- Second commit: - Rewrite to remove the word "buffer" [skip ci]
* | capitalize titleXavier Noria2015-04-201-1/+1
| | | | | | | | | | | | | | | | According to the guidelines: http://guides.rubyonrails.org/ruby_on_rails_guides_guidelines.html#headings References #19821.
* | correct link to Generic template [ci skip]yuuji.yaginuma2015-04-201-1/+1
| |
* | Consistency: Rails master -> edge Rails [ci skip]Godfrey Chan2015-04-201-1/+1
| |
* | Fix typos in contributing guide [ci skip]Godfrey Chan2015-04-191-2/+2
| | | | | | | | | | * includes -> include * "on your computer" is implied
* | Better explain the bug report templates [ci skip]Godfrey Chan2015-04-191-9/+13
|/
* Fix typos and improve the documentationJon Atack2015-04-151-8/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This is a squash of the following commits, from first to last: - Fix minor, random things I’ve come across lately that individually did not seem worth making a PR for, so I saved them for one commit. One common error is using “it’s” (which is an abbreviation of “it is”) when the possessive “its” should be used for indicating possession. - Changes include the name of a test, so remove the `[skip ci]` (thanks @senny). - Line wrap the changes at 80 chars and add one more doc fix. - Add a missing line wrap in the Contributing to Ruby on Rails Guide. - Line wrap the `TIP` section in the Contributing to Ruby on Rails Guide as well. Rendering the guide locally with `bundle exec rake guides:generate` did not show any change in on-screen formatting after adding the line wrap. The HTML generated is (extra line added to illustrate where the line wrap takes place): <div class="info"><p>Please squash your commits into a single commit when appropriate. This simplifies future cherry picks and also keeps the git log clean.</p></div> - Squash commits.
* [ci skip] Update contributing guideIslam Wazery2015-04-121-2/+2
|
* [ci skip] Subject-verb agreementJoel Brewer2015-03-141-1/+1
|
* Remove line wrapping from the benchmark/ips outputPiotr Szotkowski2015-03-031-4/+4
| | | | [ci skip]
* Talk about Gemfile.lock in the contributing guideRafael Mendonça França2015-02-181-3/+7
| | | | [ci skip]
* Doc: run bundle update after cloning Rails.Brian Morearty2015-01-291-0/+8
|
* Changed "in GitHub" to "on GitHub" [ci skip]Prathamesh Sonpatki2015-01-141-1/+1
| | | | - Followup of https://github.com/rails/rails/pull/18503.
* - Changed `IN` to `ON` in markdown renderer conditionVipul A M2015-01-141-1/+1
| | | | - Changed `IN` to `ON` in all note sentences in guides.
* Minor documentation edits [ci skip]Robin Dupret2014-12-281-3/+3
|
* warn about reading guides in GitHubXavier Noria2014-12-231-0/+2
| | | | References #18148.
* Clarify ActiveRecord testing guidelines [ci skip]Sammy Larbi2014-12-211-1/+6
| | | | | | | | | | | 1. Specify that you need to create the test databases, and that no special Rails command needs to be run to do that. 2. Although the underscore style of `rake test_mysql` works, make the documentation of running the tests in RUNNING_UNIT_TESTS.rdoc consistent with the "Contributing..." guide. 3. Promote "Testing Active Record" to not be a subsection of "Running a Single Test," since it doesn't make sense as a subsection of that.
* Fix sentence structure [ci skip]Brooks Reese2014-12-051-1/+1
|
* remove misleading class [ci skip]Sergey Alekseev2014-12-041-1/+1
|
* Oops, missed a closing bracket [ci skip]Godfrey Chan2014-10-211-1/+1
|
* [ci skip] Provide more reasoning to not accept cosmetic changesTu Hoang2014-10-211-1/+1
|
* [CI SKIP] Improve force push note.Guo Xiang Tan2014-09-231-5/+5
|
* Added note about updating pull requests by force pushPrathamesh Sonpatki2014-09-231-0/+17
| | | | | | - Added note about force pushing same branch to update a existing pull request instead of opening new one in contributing guide. - [ci skip]
* Remove more references to respond_withJosé Valim2014-08-171-1/+1
|
* docs, add example for running a single test against core adapters.Yves Senn2014-07-221-0/+6
| | | | [ci skip]
* correct markdown usage [ci skip]Nishant Modak2014-07-091-3/+1
|
* [ci skip] Add benchmark your code section to contributing to ruby on rails ↵Juanito Fatas2014-05-271-0/+30
| | | | | | | guide. I have seen many times that maintainers want people to use this gem to give a benchmark report. It would be nice to add it and refer to it later.
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-16 02:26:56 +0000