Hey everyone, For those of you who contribute to docrails, I''m trying to get a sense for the crowd-favorite git workflow. I found http://www.slideshare.net/martinsvalin/contribute-to-rails suggesting that it be added as a remote and pulled into another branch off an already-cloned rails repo. This worked fine for me, and I was able to push changes, but I''m wondering if cloning docrails separately is more commonplace (or if there are any hazards with the method I used). The guides are ambiguous in this area and I''d love to update them to cover this once I hear from the community. Thanks, Tim -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To view this discussion on the web visit https://groups.google.com/d/msg/rubyonrails-core/-/mCWapaXPMHoJ. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
I have always cloned docrails separately. -- James Gifford 2162238574 On Jan 7, 2013, at 13:00, Tim Raymond <xtjraymondx@gmail.com> wrote:> Hey everyone, > > For those of you who contribute to docrails, I''m trying to get a sense for the crowd-favorite git workflow. I found http://www.slideshare.net/martinsvalin/contribute-to-rails suggesting that it be added as a remote and pulled into another branch off an already-cloned rails repo. This worked fine for me, and I was able to push changes, but I''m wondering if cloning docrails separately is more commonplace (or if there are any hazards with the method I used). The guides are ambiguous in this area and I''d love to update them to cover this once I hear from the community. > > Thanks, > Tim > -- > You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. > To view this discussion on the web visit https://groups.google.com/d/msg/rubyonrails-core/-/mCWapaXPMHoJ. > To post to this group, send email to rubyonrails-core@googlegroups.com. > To unsubscribe from this group, send email to rubyonrails-core+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.-- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
I have always cloned it separately as well. Cheers, Gosha Arinich On Monday, January 7, 2013 at 10:45 PM, James Gifford wrote:> I have always cloned docrails separately. > > -- > James Gifford > 2162238574 > > > On Jan 7, 2013, at 13:00, Tim Raymond <xtjraymondx@gmail.com (mailto:xtjraymondx@gmail.com)> wrote: > > > Hey everyone, > > > > For those of you who contribute to docrails, I''m trying to get a sense for the crowd-favorite git workflow. I found http://www.slideshare.net/martinsvalin/contribute-to-rails suggesting that it be added as a remote and pulled into another branch off an already-cloned rails repo. This worked fine for me, and I was able to push changes, but I''m wondering if cloning docrails separately is more commonplace (or if there are any hazards with the method I used). The guides are ambiguous in this area and I''d love to update them to cover this once I hear from the community. > > > > Thanks, > > Tim > > > > -- > > You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. > > To view this discussion on the web visit https://groups.google.com/d/msg/rubyonrails-core/-/mCWapaXPMHoJ. > > To post to this group, send email to rubyonrails-core@googlegroups.com (mailto:rubyonrails-core@googlegroups.com). > > To unsubscribe from this group, send email to rubyonrails-core+unsubscribe@googlegroups.com (mailto:rubyonrails-core+unsubscribe@googlegroups.com). > > For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en. > -- > You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. > To post to this group, send email to rubyonrails-core@googlegroups.com (mailto:rubyonrails-core@googlegroups.com). > To unsubscribe from this group, send email to rubyonrails-core+unsubscribe@googlegroups.com (mailto:rubyonrails-core+unsubscribe@googlegroups.com). > For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.-- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
Separate repo here as well. On Mon, Jan 7, 2013 at 5:50 PM, Gosha Arinich <me@goshakkk.name> wrote:> I have always cloned it separately as well. > > Cheers, > Gosha Arinich > > On Monday, January 7, 2013 at 10:45 PM, James Gifford wrote: > > I have always cloned docrails separately. > > -- > James Gifford > 2162238574 > > On Jan 7, 2013, at 13:00, Tim Raymond <xtjraymondx@gmail.com> wrote: > > Hey everyone, > > For those of you who contribute to docrails, I''m trying to get a sense for > the crowd-favorite git workflow. I found > http://www.slideshare.net/martinsvalin/contribute-to-rails suggesting > that it be added as a remote and pulled into another branch off an > already-cloned rails repo. This worked fine for me, and I was able to push > changes, but I''m wondering if cloning docrails separately is more > commonplace (or if there are any hazards with the method I used). The > guides are ambiguous in this area and I''d love to update them to cover this > once I hear from the community. > > Thanks, > Tim > > -- > You received this message because you are subscribed to the Google Groups > "Ruby on Rails: Core" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/rubyonrails-core/-/mCWapaXPMHoJ. > To post to this group, send email to rubyonrails-core@googlegroups.com. > To unsubscribe from this group, send email to > rubyonrails-core+unsubscribe@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/rubyonrails-core?hl=en. > > -- > You received this message because you are subscribed to the Google Groups > "Ruby on Rails: Core" group. > To post to this group, send email to rubyonrails-core@googlegroups.com. > To unsubscribe from this group, send email to > rubyonrails-core+unsubscribe@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/rubyonrails-core?hl=en. > > > -- > You received this message because you are subscribed to the Google Groups > "Ruby on Rails: Core" group. > To post to this group, send email to rubyonrails-core@googlegroups.com. > To unsubscribe from this group, send email to > rubyonrails-core+unsubscribe@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/rubyonrails-core?hl=en. >-- At. Carlos Antonio -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
Continue the chorus of ''separate''. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
I used to use a separate remote because it was much faster than having to clone twice. But I barely worked in the Rails source itself so it made sense to me. If I worked more often on the code base itself then I''d probably keep different directories for them. Em 07/01/2013 17:40, "Tim Raymond" <xtjraymondx@gmail.com> escreveu:> Hey everyone, > > For those of you who contribute to docrails, I''m trying to get a sense for > the crowd-favorite git workflow. I found > http://www.slideshare.net/martinsvalin/contribute-to-rails suggesting > that it be added as a remote and pulled into another branch off an > already-cloned rails repo. This worked fine for me, and I was able to push > changes, but I''m wondering if cloning docrails separately is more > commonplace (or if there are any hazards with the method I used). The > guides are ambiguous in this area and I''d love to update them to cover this > once I hear from the community. > > Thanks, > Tim > > -- > You received this message because you are subscribed to the Google Groups > "Ruby on Rails: Core" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/rubyonrails-core/-/mCWapaXPMHoJ. > To post to this group, send email to rubyonrails-core@googlegroups.com. > To unsubscribe from this group, send email to > rubyonrails-core+unsubscribe@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/rubyonrails-core?hl=en. >-- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.