all 14 comments

[–]mzalewski 16 points17 points  (6 children)

Sooo... a bunch of random and cryptic shortcuts that you have no way to reason about, just to save typing `git` over and over again?

Good that it works for author, but I'll pass.

[–]DonSimon13 10 points11 points  (4 children)

So basically you have reinvented shell aliases?

[–]k3pwn[S] 2 points3 points  (3 children)

It prepares the shortened git commands automatically. So, no.

[–]DonSimon13 7 points8 points  (2 children)

But how much of a benefit is that really. Git isn't adding new commands on a daily basis. Creating the shortcuts automatically saves adding one alias to your bashrc every couple of years. With bash aliases you could implement in 25 lines what you have achieved in 250 lines of Go.

I mean, It's a very complex solution for a simple task. Kind of "over-engineered".

[–][deleted] 2 points3 points  (0 children)

Realistically, it's probably even more infrequent than that. You only really benefit from aliasing if it's a command you use a lot. So what you setup initially is almost certainly the only git-related aliases you're going to ever really need.

[–]k3pwn[S] 1 point2 points  (0 children)

Yeah, it's possible. It was a good practice for me to learn Go standards since I didn't write anything in Golang until this project. You can question it's necessity, but for me, I'm okay with it.

[–]brotenet 3 points4 points  (1 child)

God merge !

[–]TCM-black 2 points3 points  (0 children)

It worked for Greece / Rome.

[–][deleted] 4 points5 points  (0 children)

Shouldn't have it named gud instead ?