-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature request: optional organization argument to fork
, etc.
#505
Comments
Good idea. We could support something like:
|
Yeah, that would be perfect. |
👍 nice! |
👍 |
This is something I'd love to see too 👍 |
👍 |
1 similar comment
👍 |
+1 but this seems like a bug, not a feature |
👍 |
👍 cc: @mrjcleaver |
@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. |
👍 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. |
👍 |
Is anyone working on this? If not I might take a stab at it. |
@sjmulder You're welcome to take a stab at it! |
Currently,
hub fork
andhub 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.
The text was updated successfully, but these errors were encountered: