On Wednesday, March 2, 2011 3:53:40 PM UTC-8, Chris Wanstrath wrote: > > On Wednesday, March 2, 2011 at 3:47 PM, Jacob Biesinger wrote: > I guess the best way to handle this is to Fork their GitHub repo as a new > repo, then rebase my initial import on the forked repo? Is that enough for > GitHub to recognize the fork? > You could do that, or you can email sup...@github.com with the relevant > URLs and we'll mark your project as a fork of the other project. >
I'm expecting to push/pull between forks a fair bit. Would the former option be cleaner (especially from a Fork Queue point of view)? They have several changes from my initial commit which I've already merged into my code, and since they weren't using a DVCS before, the commits that have brought their branch to its current point, (which I've already merged into my code), will have different ID's. What's the cleanest way from here on out? -- You received this message because you are subscribed to the Google Groups "GitHub" group. To post to this group, send email to github@googlegroups.com. To unsubscribe from this group, send email to github+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/github?hl=en.
