search for: godfreykfc

I''m probably going to help backport some code from master onto 3.2, and the suggested process in the Contributing guide doesn''t actually look like the best approach to me. Wouldn''t it make more sense to just check out the branch you want to patch, cherry-pick the change(s) from master, make any additional commits necessary to get it working? Not only is that simpler

Hi Folks, There is much discussion where I work at present regarding migrations, and the ''correct'' usage or not of them. TL;DR Should migrations be used just to modify schema, and other ''deploy'' tasks done other ways? If yes, how to ensure no repeat runs of such tasks (seeds, jobs etc) Background Once you''re live there are often additional things

Hi all, I talked to Aaron briefly about this at RailsConf, but I just wanted to bring this up here before I start working on it in case anyone objects. I will be looking into moving the "Plural version of the model detected, using singularized version. Override with --force-plural." warning and the associated flag into the model generators. Currently this is only in the resource (and