Skip to content


Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Commits on Nov 1, 2012
  1. @steveklabnik
Commits on Oct 29, 2012
  1. @rafaelfranca

    Merge pull request #7587 from elia/fix-too-eager-loading

    rafaelfranca authored
    Should not eager_load app/assets
Commits on Oct 13, 2012
  1. @jeremy
Commits on Oct 12, 2012
  1. @bjnord
Commits on Oct 9, 2012
  1. @blowmage

    Update test locations

    blowmage authored
    Change the default test locations to avoid confusion around the common
    testing terms "unit" and "functional".
    Add new rake tasks for the new locations, while maintaining backwards
    compatibility with the old rake tasks.
    New testing locations are as follows:
        app/models -> test/models (was test/units)
        app/helpers -> test/helpers (was test/units/helpers)
        app/controllers -> test/controllers (was test/functional)
        app/mailers -> test/mailers (was test/functional)
  2. @guilleiguaran
Commits on Oct 3, 2012
  1. @sikachu
Commits on Sep 19, 2012
  1. @guilleiguaran

    Remove highly uncommon `config.assets.manifest` option for moving the…

    guilleiguaran authored
    … manifest path.
    This option is now unsupported in sprockets-rails.
  2. @guilleiguaran
Commits on Sep 13, 2012
  1. @derekprior @frodsan

    change app/plugin generators to be more SCM agnostic

    derekprior authored frodsan committed
    Users of other SCM's can now generate rails
    apps that will add the "empty" directories to source control,
    but will not have a useless .gitignore or mis-named .gitkeep
    * Change `rails new` and `rails plugin new` generators to name
      the `.gitkeep` as `.keep` in a more SCM-agnostic way.
    * Change `--skip-git` option to only skip the `.gitignore` file
      and still generate the `.keep` files.
    * Add `--skip-keeps` option to skip the `.keep` files.
    It closes #2800.
Commits on Sep 12, 2012
  1. @graceliu

    fixed support for DATABASE_URL for rake db tasks

    graceliu authored
    - added tests to confirm establish_connection uses DATABASE_URL and
      Rails.env correctly even when no arguments are passed in.
    - updated rake db tasks to support DATABASE_URL, and added tests to
      confirm correct behavior for these rake tasks.  (Removed
      establish_connection call from some tasks since in those cases
      the :environment task already made sure the function would be called)
    - updated Resolver so that when it resolves the database url, it
      removes hash values with empty strings from the config spec (e.g.
      to support connection to postgresql when no username is specified).
Commits on Sep 10, 2012
  1. @needfeed
Commits on Aug 28, 2012
  1. @fxn

    CHANGELOGs are now per branch

    fxn authored
    Changes in old branches needed to be manually synched in CHANGELOGs of newer ones.
    This has proven to be brittle, sometimes one just forgets this manual step.
    With this commit we switch to CHANGELOGs per branch. When a new major version is
    cut from master, the CHANGELOGs in master start being blank.
    A link to the CHANGELOG of the previous branch allows anyone interested to
    follow the history.
Commits on Aug 21, 2012
  1. @josevalim
Commits on Aug 10, 2012
  1. @drogus

    Fix handling SCRIPT_NAME from within mounted engine's

    drogus authored
    When you mount your application at a path, for example /myapp, server
    should set SCRIPT_NAME to /myapp. With such information, rails
    application knows that it's mounted at /myapp path and it should generate
    routes relative to that path.
    Before this patch, rails handled SCRIPT_NAME correctly only for regular
    apps, but it failed to do it for mounted engines. The solution was to
    hardcode default_url_options[:script_name], which is not the best answer
    - it will work only when application is mounted at a fixed path.
    This patch fixes the situation by respecting original value of
    SCRIPT_NAME when generating application's routes from engine and the
    other way round - when you generate engine's routes from application.
    This is done by using one of 2 pieces of information in env - current
    SCRIPT_NAME or SCRIPT_NAME for a corresponding router. This is because
    we have 2 cases to handle:
    - generating engine's route from application: in this situation
      SCRIPT_NAME is basically SCRIPT_NAME set by the server and it
      indicates the place where application is mounted, so we can just pass
      it as :original_script_name in url_options. :original_script_name is
      used because if we use :script_name, router will ignore generating
      prefix for engine
    - generating application's route from engine: in this situation we
      already lost information about the SCRIPT_NAME that server used. For
      example if application is mounted at /myapp and engine is mounted at
      /blog, at this point SCRIPT_NAME is equal /myapp/blog. Because of that
      we need to keep reference to /myapp SCRIPT_NAME by binding it to the
      current router. Later on we can extract it and use when generating url
    Please note that starting from now you *should not* use
    default_url_options[:script_name] explicitly if your server already
    passes correct SCRIPT_NAME to rack env.
    (closes #6933)
Commits on Aug 7, 2012
  1. @dhh

    Revert "The application generator generates `public/humans.txt` with …

    dhh authored
    …some basic data". I dont consider this something most people is going to want most of the time. If you want to add it in your own app, knock yourself out. But it doesnt belong in Rails imo
Commits on Jul 8, 2012
  1. @lexmag

    Add references statements to migration generator

    lexmag authored
    AddXXXToYYY/RemoveXXXFromYYY migrations are produced with references
    statements, for instance
        rails g migration AddReferencesToProducts user:references
    will generate the migration with:
        add_reference :products, :user, index: true
        add_reference :products, :supplier, polymorphic: true, index: true
Commits on Jun 27, 2012
  1. @carlosantoniodasilva
Commits on Jun 23, 2012
  1. @bcardarella

    Updated Changelogs

    bcardarella authored
Commits on Jun 10, 2012
  1. @josevalim
Commits on May 30, 2012
  1. @kennyj
Commits on May 24, 2012
  1. @schneems

    /rails/info/routes path shows routing information

    schneems authored
    Will show similar contents to the output of `$ rake routes` in the browser in development. This speeds the time required to generate routes, since the application is already initialized.
Commits on May 19, 2012
  1. @pixeltrix
Commits on May 16, 2012
  1. @drogus
Commits on May 8, 2012
  1. @fxn

    registers ceb1dcc in the CHANGELOG

    fxn authored
Commits on May 4, 2012
  1. @carlosantoniodasilva
Commits on Mar 17, 2012
  1. @rafaelfranca
Commits on Mar 13, 2012
  1. @sikachu

    Remove Active Resource source files from the repository

    sikachu authored
    Dear Active Resource,
    It's not that I hate you or anything, but you didn't get much attention lately. There're so many alternatives out there, and I think people have made their choice to use them than you. I think it's time for you to have a big rest, peacefully in this Git repository.
    I will miss you,
Commits on Mar 9, 2012
  1. @rafaelfranca

    Fix my name in the CHANGELOG to follow the convention

    rafaelfranca authored
    Also add missing entries and use the formating convention
Commits on Mar 1, 2012
  1. @claudiob

    Add release dates to documentation

    claudiob authored
    Set "March 1, 2012" as the release date for 3.2.2, 3.1.4, 3.0.12
Commits on Feb 25, 2012
  1. @pacoguzman

    Update changelogs with rails 3.0-stable branch info

    pacoguzman authored pacoguzman committed
  2. @fxn

    uses PATCH for the forms of persisted records, and routes PATCH and P…

    fxn authored
    …UT to the update action of resources
Commits on Feb 22, 2012
  1. @fxn
Commits on Feb 16, 2012
  1. @drogus

    Allow to set custom console type with Rails.application.config.console=

    drogus authored
    This patch adds ability to set custom console if you want to use
    something other than IRB. Previously the hack that people used
        silence_warnings do
          require 'pry'
          IRB = Pry
    which is not the best way to customize things.
Commits on Feb 3, 2012
  1. @carlosantoniodasilva

    Add convenience method to hide a generator from the available ones

    carlosantoniodasilva authored
    It is usually useful to be able to hide a generator when running rails
    generate command. Such generators might be used only to dry up
    generators code and shouldn't be available to end users.
Something went wrong with that request. Please try again.