Git-repo – Manage Gitlab, GitHub and Bitbucket from the command line • Hacker News Board

Re: Git-repo – Manage Gitlab, GitHub and Bitbucket from the command line

#11

Post by Aldo_MX » Mon, Oct 10, 2016, 5:24 PM UTC

KZeillmann wrote: post #7

I 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 to dig further in the documentation or look for an external reference to understand what's the real purpose behind a product, tool or service.

Re: Git-repo – Manage Gitlab, GitHub and Bitbucket from the command line

#12

Post by seschwar » Mon, Oct 10, 2016, 5:27 PM UTC

There'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

#13

Post by icebraining » Mon, Oct 10, 2016, 5:31 PM UTC

0xmohit wrote: post #9

then 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?

  poweroff: Need to be root

Re: Git-repo – Manage Gitlab, GitHub and Bitbucket from the command line

#14

Post by adamnemecek » Mon, Oct 10, 2016, 5:32 PM UTC

azdavis wrote: post #4

adamnemecek wrote: post #2

I'm surprised Github et al. haven't tried to contribute some functionality for doing this to git. The thing described in the article is extremely common.

They have, sort of. https://hub.github.com

Do you use it?

Re: Git-repo – Manage Gitlab, GitHub and Bitbucket from the command line

#15

Post by 0xmohit » Mon, Oct 10, 2016, 5:35 PM UTC

icebraining wrote: post #13

0xmohit wrote: post #9

then 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?

poweroff: Need to be root

One might have sudo privileges configured via /etc/sudoers (It's the default on AWS EC2 instances!)

Re: Git-repo – Manage Gitlab, GitHub and Bitbucket from the command line

#16

Post by prh8 » Mon, Oct 10, 2016, 5:38 PM UTC

I really like that this works for all services interchangeably. Yes, Github created Hub for this same problem, but I've used Bitbucket at some jobs and Gitlab personally for some projects. Having something uniform and service agnostic is great. It's clear the creator thought a lot about this design feature.

Re: Git-repo – Manage Gitlab, GitHub and Bitbucket from the command line

#17

Post by cmrx64 » Mon, Oct 10, 2016, 5:48 PM UTC

adamnemecek wrote: post #14

azdavis wrote: post #4

Earlier quoted context omitted.

They have, sort of. https://hub.github.com

Do you use it?

I use hub whenever working with GitHub. It's quite nice, since the rewrite in Go.

Re: Git-repo – Manage Gitlab, GitHub and Bitbucket from the command line

#18

Post by icebraining » Mon, Oct 10, 2016, 5:54 PM UTC

0xmohit wrote: post #15

icebraining wrote: post #13

Earlier quoted context omitted.

poweroff: Need to be root

One might have sudo privileges configured via /etc/sudoers (It's the default on AWS EC2 instances!)

Yes, but you still need to call "sudo poweroff", not just "poweroff".

Re: Git-repo – Manage Gitlab, GitHub and Bitbucket from the command line

#19

Post by zerocrates » Mon, Oct 10, 2016, 5:58 PM UTC

azdavis wrote: post #8

michaelmior wrote: post #5

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

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

#20

Post by chainsaw10 » Mon, Oct 10, 2016, 6:15 PM UTC

icebraining wrote: post #13

0xmohit wrote: post #9

then 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?

poweroff: Need to be root

Some recent distros will actually let you run that as yourself, without root, if you're physically present at the machine. It's convenient for personal machines.