#1494 Make rails:update task update new initializers - Ruby on Rails

Type	To find
responsible:me	tickets assigned to you
tagged:"@high"	tickets tagged @high
milestone:next	tickets in the upcoming milestone
state:invalid	tickets with the state invalid
created:"last week"	tickets created last week
sort:number, importance, updated	tickets sorted by #, importance or updated
Combine keywords for powerful searching.
Use advanced searching »

This project is archived and is in readonly mode.

#1494 ✓stale

Make rails:update task update new initializers

Reported by Juan Lupión | November 29th, 2008 @ 07:15 PM | in 3.x

An easy one: just found that freezing to Rails edge and running rails:update didn't create the new backtrace_silencers.rb, this fixes it by adding a new task to copy any new initializers to config/initializers without overwriting existing ones.

update_initializers.diff 1.8 KB

Comments and changes to this ticket

You flagged this item as spam.
Juan Lupión November 29th, 2008 @ 07:19 PM
- Title changed from “[PATCH] Make rails:update task update new initializers” to “Make rails:update task update new initializers”
Pratik December 22nd, 2008 @ 11:43 AM
- Assigned user set to “Pratik”
- State changed from “new” to “incomplete”
Looks good to me. However, it shouldn't copy new_rails_defaults.rb

Thanks.
You flagged this item as spam.
Juan Lupión January 11th, 2009 @ 07:38 PM
This should make it now.
- update_initializers_modulo_new_rails_defaults.diff 1.7 KB
You flagged this item as spam.
Josh Nichols August 19th, 2009 @ 01:00 AM
I tried applying this patch to master, but it didn't result in any changes. Probably can mark this wontfix, already fixed, or something like that.
Jeremy Kemper May 4th, 2010 @ 06:48 PM
- Milestone changed from “2.x” to “3.x”
[bulk edit]
rails May 4th, 2011 @ 01:00 AM
- State changed from “incomplete” to “open”
This issue has been automatically marked as stale because it has not been commented on for at least three months.

The resources of the Rails core team are limited, and so we are asking for your help. If you can still reproduce this error on the 3-0-stable branch or on master, please reply with all of the information you have about it and add "[state:open]" to your comment. This will reopen the ticket for review. Likewise, if you feel that this is a very important feature for Rails to include, please reply with your explanation so we can consider it.

Thank you for all your contributions, and we hope you will understand this step to focus our efforts where they are most helpful.
rails May 4th, 2011 @ 01:00 AM
- State changed from “open” to “stale”