Git-repo – Manage Gitlab, GitHub and Bitbucket from the command line
21–30 of 70 posts
Re: Git-repo – Manage Gitlab, GitHub and Bitbucket from the command line
#22I really enjoy how the author broke down both the problem and the solution, explaining why the existing solutions are inadequate. I often see articles about new products or new programming languages, and their features, but they often forget to mention what problem prompted the solution. Why was a new language invented to solve this problem? Why were the existing solutions limiting? Bravo to the author here for makin…
> I really enjoy how the author broke down both the problem and the solution, explaining why the existing solutions are inadequate. A thousand times this, I always get frustrated that every single product, tool or service has to have a lot of marketing gibberish, catchy slogans, etc., but zero explanations of what problems do they attempt to solve, or what was the motivation to create them. You usually are required t…
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 invent the DIFY concept, to override the DIY concept )… only then I'm sharing it with others.
Re: Git-repo – Manage Gitlab, GitHub and Bitbucket from the command line
#23I 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
What git-repo really offers is a tool that integrates nicely to the git CLI (as `git-something` is also available as `git something`, so git-repo acts per default as `git repo hub…`). And then it autoconfigures the .gitconfig aliases to have the `git hub`, `git lab`, `git moo` you'd want.
So besides the fact that hub is certainly much more mature than my tool, it wouldn't be a tool I'd like to really use.
Re: Git-repo – Manage Gitlab, GitHub and Bitbucket from the command line
#24then you watch the code, create a branch: git checkout -b `bugfix/nasty_one` Please remove backticks from the command. What if you called the branch `poweroff` instead and a naive reader copy/pasted the command into her terminal?
Re: Git-repo – Manage Gitlab, GitHub and Bitbucket from the command line
#25Cool 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/
I hope that if people like the tool, it's going to be easier to find.
Of course, I'm not really obsessed with the name (as anyway the tool is designed so the user does not type git-repo everyday ). So if someone comes up with a name that's great that can be better, I'm all ears!
About the fact that google has that other tool… Well they really are not much projects using it, beyond the google projects, and the tool really is called `repo`, not `git-repo`, so the name clash is not really there.
Re: Git-repo – Manage Gitlab, GitHub and Bitbucket from the command line
#26Feature request - Add the ability to create a merge request from command line. Esp for GitLab
https://github.com/guyzmo/git-repo/commit/59c7ac2cd4c0316016...
So pretty soon I hope I'll be able to finish both MR and snippets for gitlab, and finish the tests and merge all that back to git-repo!
Re: Git-repo – Manage Gitlab, GitHub and Bitbucket from the command line
#27There's also git-spindle for this: - https://seveas.github.io/git-spindle/ - https://github.com/seveas/git-spindle
Re: Git-repo – Manage Gitlab, GitHub and Bitbucket from the command line
#28This is wonderful. I'd guess that this little tiny bit of extra friction is enough of a disturbance to the workflow for private local/personal/work projects to prevent many from bothering to contribute back in some cases (I'm definitely guilty here).
Re: Git-repo – Manage Gitlab, GitHub and Bitbucket from the command line
#29I see references to lab and hub, is bitbucket missing?
Re: Git-repo – Manage Gitlab, GitHub and Bitbucket from the command line
#30Earlier quoted context omitted.
> I really enjoy how the author broke down both the problem and the solution, explaining why the existing solutions are inadequate. A thousand times this, I always get frustrated that every single product, tool or service has to have a lot of marketing gibberish, catchy slogans, etc., but zero explanations of what problems do they attempt to solve, or what was the motivation to create them. You usually are required t…
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…
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 ;)