Currently, hub fork
and hub pull-request
only will create forks in [user]/[repo].
I'd really like to be able to (optionally) fork the project under an [organization]/[repo].
There are a number of reasons why this would make sense, but here's mine: I always put projects for which I'm submitting PRs into an organization I've created for this particular purpose since, well, some people aren't so good at following up on PRs in a timely manner; and I prefer not to clutter up "my" repos with a bunch of forks which need to remain for an indeterminate length of time.
I'd hack on this myself, but for the "hub's gonna go go" business.
Good idea. We could support something like:
git fork --org <name>
Yeah, that would be perfect.
:+1: nice!
:+1:
This is something I'd love to see too :+1:
:+1:
:+1:
+1 but this seems like a bug, not a feature
:+1:
:+1:
cc: @mrjcleaver
Counting the dup and the naked +1, I believe that makes a full :raised_hands:, does it not?
@rtomayko? @mislav? @bueller?
Or, I could stfu and go get me some effective golang, which is probably what I should be doing anyway.
@geoff-codes Here is the line where forking happens. If this feature was to happen, then we should add a configuration option that accepts a name of an org that affects the fork operation.
:+1: this feature would be awesome.
Having a fork of a project as a separate code and still being able to do PR across would be very useful.
:+1:
Is anyone working on this? If not I might take a stab at it.
@sjmulder You're welcome to take a stab at it!
Most helpful comment
Is anyone working on this? If not I might take a stab at it.