Skip to content


Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Commits on May 2, 2015
  1. @prathamesh-sonpatki

    Removed `assigns` from functional_test templates

    prathamesh-sonpatki authored
     - Based on DHH's suggestion about deprecating `assigns` in
       #18305 (comment).
Commits on Apr 26, 2015
  1. @prathamesh-sonpatki

    Escape README in Plugin builder API documentation

    prathamesh-sonpatki authored
     - So that RDoc will not generate link for README.
     [ci skip]
Commits on Apr 25, 2015
  1. @amatsuda

    Do not show --helper and --assets options in the controller generator…

    amatsuda authored
    … help
    These options are not actually available.
    Thanks @soutaro for letting me aware of this.
Commits on Apr 22, 2015
  1. @rafaelfranca

    Merge pull request #19858 from cllns/fix-scaffolding-css-formatting

    rafaelfranca authored
    Fix formatting of scaffold css
  2. @cllns

    Fix formatting of scaffold css

    cllns authored
Commits on Apr 20, 2015
  1. @cllns
  2. @chancancode

    Implicitly skip spring for `rails new --dev`

    chancancode authored
    Spring seems like an obvious foot gun for the `--dev` setup, presumably you are
    about to make lots of changes to the codebase, so it should always reload the
Commits on Apr 14, 2015
  1. @y-yagi

    fix indent in routes when using namespaced controllers

    y-yagi authored
      namespace :foo do
      namespace :bar do
        get 'baz/index'
      namespace :foo do
        namespace :bar do
          get 'baz/index'
Commits on Apr 7, 2015
  1. @rafaelfranca

    Avoid to define an initializer after the load_config_initializers

    rafaelfranca authored
    This make the config/initializers run before the railties are loaded
    what can break some configurations.
Commits on Apr 3, 2015
  1. @matthewd

    Merge pull request #19429 from mxhold/print_bundle_install_output_lin…

    matthewd authored
    Print `bundle install` output in `rails new` as soon as it's available
Commits on Mar 31, 2015
  1. @y-yagi
Commits on Mar 30, 2015
  1. @matthewd

    Merge pull request #19034 from jvanbaarsen/explicit-job-base-class

    matthewd authored
    Add explicit base class for ActiveJob jobs
Commits on Mar 28, 2015
  1. @mxhold

    Print `bundle install` output in `rails new` as soon as it's available

    mxhold authored
    Previously, running `rails new` would not print any of the output from
    `bundle install` until all the gems had finished installing. This made
    it look like the generator was hanging at the `bundle install` step.
    This commit switches to using `system` so that the bundle command can
    output as it needs to.
    This has the added benefit of including output bundler produces on
    standard error, which the previous code ignored since backticks only
    capture standard out. This is not a big deal right now since bundler
    does not currently print errors to standard error, but that may change
    in the future (see: bundler/bundler#3353).
Commits on Mar 27, 2015
  1. @y-yagi
Commits on Mar 23, 2015
  1. @jvanbaarsen

    Add explicit base class for ActiveJob jobs

    jvanbaarsen authored
    * Jobs generated now inherent from ApplicationJob
    * ApplicationJob inherents from ActiveJob::Base
    * Added entry to changelog
    Signed-off-by: Jeroen van Baarsen <>
Commits on Mar 19, 2015
  1. @amitsuroliya
  2. @arthurnn
Commits on Mar 18, 2015
  1. @arthurnn

    Add a new-line to the end of route method generated code.

    arthurnn authored
    Fix regression on route method that was added by
    bac812a. The regression was that when
    calling the `route` method, we were not appending a \n anymore.
    [fixes #19316]
Commits on Mar 14, 2015
  1. @y-yagi
Commits on Mar 13, 2015
  1. @josh @rafaelfranca

    Update sprockets links to point to rails org

    josh authored rafaelfranca committed
Commits on Feb 21, 2015
  1. @simi

    Require `belongs_to` by default.

    simi authored
    Deprecate `required` option in favor of `optional` for belongs_to.
Commits on Feb 20, 2015
  1. @rafaelfranca
Commits on Feb 19, 2015
  1. @meganemura
Commits on Feb 18, 2015
  1. @rafaelfranca
  2. @rafaelfranca

    Revert "Merge pull request #18951 from jurezove/gemfile-lock-to-plugi…

    rafaelfranca authored
    This reverts commit b824dfd, reversing
    changes made to 265dcb7.
    Our general recommendation is to check in the lock file in the
    This make possible to developers and contributors of a plugin always run
    their tests against a working set of dependencies.
    Also, bisect is a lot easier, specially if you have git dependencies in your
Commits on Feb 15, 2015
  1. @jurezove
Commits on Feb 8, 2015
  1. @yuki24

    Remove warning from Plugin Generator

    yuki24 authored
    This removes the following warning:
      rails/railties/lib/rails/generators/rails/plugin/plugin_generator.rb:321: warning: shadowing outer local variable - content
Commits on Feb 6, 2015
  1. @fxn

    README.rdoc -> for newly generated applications

    fxn authored
    README.rdoc was generated to support the doc:app task. Now that
    this task is gone we can switch to Markdown, which is nowadays
    a better default.
  2. @fxn

    Remove documentation tasks

    fxn authored
    This patch removes the tasks doc:app, doc:rails, and doc:guides.
    In our experience applications do not generate APIs using doc:app.
    Methods may be certainly documented for maintainers, annotated
    with YARD tags, etc. but that is intended to be read with the
    source code, not in a separate website. Then, teams also have
    typically selected topics written down in Markdown files, or in
    a GitHub wiki... that kind of thing.
    If a team absolutely needs to generate application documentation
    for internal purposes, they can still easily write their own task.
    Regarding doc:rails and doc:guides, we live in 2015. We are used
    to go to online docs all the time. If you really want access to the
    API offline RubyGems generates it for every Rails component unless
    you tell it not to, and you can checkout the Rails source code to
    read the guides as Markdown, or download them for a Kindle reader.
    All in all, maintaining this code does not seem to be worthwhile
    As a consequence of this, guides (+3 MB uncompressed) won't be
    distributed with the rails gem anymore. Of course, guides and API
    are going to be still part of releases, since documentation is
    maintained alongside code and tests.
    Also, time permitting, this will allow us to experiment with novel
    ways to generate documentation in the Rails docs server, since
    right now we were constrained by being able to generate them in
    the user's environment.
Commits on Feb 5, 2015
  1. @rafaelfranca

    Merge pull request #18526 from vipulnsward/add-silence-stream

    rafaelfranca authored
    Extracted silence_stream method to new module in activesupport/testing
  2. @pixeltrix

    Force generated route to be inserted

    pixeltrix authored
    Thor isn't very discerning over whether some content is present when passed
    to `inject_into_file`, e.g. a commented out route is detected as being present.
    So to prevent people scratching their heads as to why a route hasn't appeared
    it's better to fall on the side of having duplicate routes.
Commits on Feb 3, 2015
  1. @pixeltrix

    Don't remove all line endings from routes.rb

    pixeltrix authored
    When there is a single scaffold in the routes.rb with no other lines
    then revoking/destroying it will create a routes.rb file with a syntax
    error. This is because the sentinel for the Thor `route` action didn't
    include the newline but the logged route code did.
    The fix is to add the newline to the sentinel and remove it from the
    the logged route code.
    Fixes #15913.
Commits on Feb 1, 2015
  1. @robertomiranda
Commits on Jan 30, 2015
  1. @chancancode

    Fixed a few things from ee9e4c3

    chancancode authored
    Mostly cosmetics, except that `isolate_namespace` should be applied to the last
    module in the chain.
  2. @robinboening

    Allow hyphenated names for `rails plugin new` generator.

    robinboening authored
    It was not possible to create a new gem with a hyphenated name via the `rails plugin new` generator.
    The naming guide of rubygems clearly says dashes should be used for gems that extend other gems.
Something went wrong with that request. Please try again.