[mst]

The same situation kinda drove me insane too, but I've been happily using -

https://github.com/ingydotnet/git-hub/

for a while now. It might be interesting to compare and contrast your tooling and git-hub - ingy's being straight bash, while a little crazy, makes installation really trivial, but then again yours supports multiple services, but then again who knows whether the different subcommand syntaxes will work better or worse for any particular other user.

(also, lest anybody think this is a veiled complaint, I'm sure ingy's reaction to finding your work exists will be "awesome, the more the merrier" followed by figuring out if you came up with any features he wants to steal ;)

[guyzmo]

Thank you, though pretty close, our approaches are slightly different. My main focus is use case, I did not implement the social features of a repository, because those are things that happen happily in a browser.

But project/merge requests/gists are things that have a lot of sense to happen in the commandline /instead/ of within the browser. So basically, his solution is more feature complete on the social side, whereas I implemented more the repository interaction side (like creating gists, or fetching a PR).

So for sure he's got a point for portability being a bash script, but still python3 is begining to be widespread enough.

I mean, if debian-stable got it, you can consider it's everywhere…

[mst]

Not sure if it's something you'd call a social feature, but I find things like listrepos on an organization to be really helpful for piping into xargs to checkout everything a new customer depends on.

The PR stuff is so far as I can see complete in git-hub - what do you think you're missing?

(edit: if you meant gists, lots of the people I know already use paste site CLIs that handle that, btw, so to -us- that's more a social feature than the existing functionality is)

[guyzmo]

My bad, I did not scroll down to see how complete the command set was. At the top of the readme the list of commands is misleading (I thought there were only those at the first read).

I'm not sure I can see a real use for checking out every repo of an organisation (I mean, if you do that with mozilla, you better start before going for a long holiday ), but having it /possible/ is a great thing

So I guess we're pretty much alike, git-repo being strong for being service agnostic, and git-hub being more complete.

Though, in my redesign plan I got for version 2, I have in mind a framework to make it possible to implement service-specific CLI API, while sharing a same core CLI API for the service-agnostic features.

So my hope is that people will like the tool enough to participate in the development and help make the tool more feature complete across the services!

[mst]

> I'm not sure I can see a real use for checking out every repo of an organisation

Maybe I wasn't explicit about it, but I did (and do) have one:

New customer with a github org and I want everything from their org so I can have a spelunk through the code while getting up to speed, build out dependency graphs to get a feel for how things interrelate, etc.

In fact, making it possible to script checking out an org's worth of perl repositories and shoving them into an http://p3rl.org/App::opan instance easily was the thing that was painful enough for me to finally install git-hub.

So, yeah, it may not be a common use case but it's actually an essential feature for me. Whether this means you should prioritise stealing it likely depends on how common it is, which I can't answer :)

[softawre]

As a bitbucket user (for work), thanks for your contribution.

[edibleEnergy]

came here to mention 'git-hub' as a "see also" as well :)