Right, I see the process is to fork rails and and make a PR with the patch. Thanks for the tips, and for the offer of further support.
On Tuesday, 4 September 2018 15:12:54 UTC+1, Xavier Noria wrote: > > On Mon, Sep 3, 2018 at 11:16 PM, 'Ryan' via Ruby on Rails: Core < > rubyonra...@googlegroups.com <javascript:>> wrote: > > Yes I'd love to contribute a patch for this. >> >> I posted it as an issue in the rails repo and they directed me here. >> https://github.com/rails/rails/issues/33771#issuecomment-417848091 >> >> Could you advise on your normal process for this? I've contributed a >> rails before, but that was for an issue someone else had created. >> > > Sure, there is a guide that might help you: > > https://edgeguides.rubyonrails.org/contributing_to_ruby_on_rails.html > > Please, don't hesitate to ask for help if the guide is not enough, feel > free to write to me directly. > > -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-core+unsubscr...@googlegroups.com. To post to this group, send email to rubyonrails-core@googlegroups.com. Visit this group at https://groups.google.com/group/rubyonrails-core. For more options, visit https://groups.google.com/d/optout.
