There's also git-spindle for this: - https://seveas.github.io/git-spindle/ - https://github.com/seveas/git-spindle
Git-repo – Manage Gitlab, GitHub and Bitbucket from the command line
31–40 of 70 posts
Re: Git-repo – Manage Gitlab, GitHub and Bitbucket from the command line
#32Re: Git-repo – Manage Gitlab, GitHub and Bitbucket from the command line
#33What about bitbucket? I see references to lab and hub, is bitbucket missing?
Re: Git-repo – Manage Gitlab, GitHub and Bitbucket from the command line
#34The site is now returning an error. I guess HN killed it?
Re: Git-repo – Manage Gitlab, GitHub and Bitbucket from the command line
#35What about bitbucket? I see references to lab and hub, is bitbucket missing?
The issue I have is that I got to implement OAuth2 for bitbucket, because the privatekey scheme offered by bitbucket does not work for a CLI tool use case. So currently, the credentials (login/password) of bitbucket are stored in CLEAR in the configuration file, which really, really sucks…
And some new features (like the snippets) are not implemented in third part python libraries, because most of the libs are old and unmaintained.
Anyway, following some discussions I had with atlassian bitbucket developers, bitbucket (like gitlab) is planning to switch to swagger, which will help automagical generation of client-side feature complete libraries. So I'm planning to level bitbucket feature set as soon as they land the new API.
So I hope it won't be long before all the features will land for the three services!
Re: Git-repo – Manage Gitlab, GitHub and Bitbucket from the command line
#36> (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.
Re: Git-repo – Manage Gitlab, GitHub and Bitbucket from the command line
#37Earlier 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…
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…
Re: Git-repo – Manage Gitlab, GitHub and Bitbucket from the command line
#38> 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.
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. Though, I'm trying my best to avoid the decade old troll about git's UX (like vs mercurial)…
In the end, what I try to make clear it's that I'm not trying to replace what git does, but cluster a bunch of repository actions tied with some service's API operations.
And I try my best to offer a pleasant UX doing so. But please, help me making it better!
Re: Git-repo – Manage Gitlab, GitHub and Bitbucket from the command line
#39Earlier quoted context omitted.
IMHO, hub works best if you alias git=hub in your shellrc.
I don't use hub much, but I prefer not to alias it even though that's what they recommend as well. I think it's best to keep them separated so you know what stuff is coming from hub and what's in vanilla git instead. "git" is already synonymous enough with "GitHub" in many peoples' minds without including GitHub-specific functionality in your mental model of the command line client.
Re: Git-repo – Manage Gitlab, GitHub and Bitbucket from the command line
#40Earlier quoted context omitted.
They have, sort of. https://hub.github.com
Do you use it?
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...