41–50 of 70 posts
Earlier quoted context omitted.
Do you use it?
No, actually, but I did (sort of) reimplement[0] the "git browse" command that hub gives you. I'd probably use hub if I was involved in more projects that didn't have me as the sole developer. [0]: https://github.com/azdavis/dotfiles/blob/master/bin/git-brow...
> The git utility has a rather well designed interface to make it easy to remember, extend, and/or customize > (which nobody does, because who remembers the git remote syntax? I wish we would move on from the "git has good UX" narrative, it's preventing us from actually improving the UX.
note that I did not say that git has a good UX, I said it's /rather well designed/… Maybe should I have emphazised on the /rather/, or used something stronger like /relatively/ . But anyway, designing the command line API of my own tool took me enough headaches — and I'm still not 100% satisfied — to understand how hard it is to have a consistent and great UX for something that offer as many features as git does. Tho…
Congratulations for making git-repo, by the way! It looks extremely useful.
There's also git-spindle for this: - https://seveas.github.io/git-spindle/ - https://github.com/seveas/git-spindle
what the… ok I totally missed that one! And I DID search before writing such a tool
Cool but 'repo' is a really hard name to search. There's already a tool by this name and they have the same problem. https://code.google.com/p/git-repo/
Earlier quoted context omitted.
thank you a lot for your comments I actually wrote that tool based on a huge frustration I had going back and forth to the browser, and not being able to work while being agnostic to the services, which felt being a totally broken UX. I have then worked on that tool for a while, used it and refactored it a lot up until I'm happy using it. All in all, when I'm doing a tool, I'm first doing it for myself (I might inven…
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 be…
Earlier quoted context omitted.
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 be…
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, whe…
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)
Earlier quoted context omitted.
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, whe…
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…
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!
I use hub[0] to accomplish some of the same things. `hub fork` creates a fork and sets up a new remote. After pushing to my fork, `hub pull-request` creates a pull request. [0] https://github.com/github/hub
Earlier quoted context omitted.
what the… ok I totally missed that one! And I DID search before writing such a tool
That's what always happens to me as well. I've attributed it to me only half-heartedly searching, because deep down I just want to write the tool.
You might see on my github that I do that a lot, I'm being some sort of mercenary of FLOSS projects, as I patch wherever I see a bug or want a new feature without really caring about the "big plan"
Actually, I wrote the tool because deep down I just want to /use/ the tool.
Earlier quoted context omitted.
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…
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…