Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

GitHub CLI 1.0

github.blog

Post reply on HN
Print view View original

41–50 of 221 posts

Re: GitHub CLI 1.0

#41

Post by ufo »

_ph_ wrote: post #23
shaky wrote: post #6

I don't understand the appeal of using a cli to manage commits, branches, remotes, merges with conflicts, and so on. To me all these things are so much better internalized and understood when presented visually. Git GUIs are aplenty (Sublime Merge being my latest discovery, SourceTree before that) and generally really good. Combined with the already amazing GitHub web GUI, it's a wonder what use case is better served…

Besides the obvious advantages of command line user interfaces for a lot of use cases, I am not aware of any really good Git GUI. Can you name any for Linux or Mac OS? Commercial would be ok, as long as it can be installed locally and does not require a server.

On Linux I like using gitg. I think it is "good" in the sence that for the tasks it can do (mostly viewing history) the UI is well though out and simple to use. However, it can't do more advanced tasks so it might not be what you are asking for.

Re: GitHub CLI 1.0

#42

Post by Galanwe »

cfors wrote: post #5
dberg wrote: post #2

Is this proof that regular git commands are too difficult to use? I also wonder what this is going to do for folks not using Github as now CLI users are going to "unlearn" all their traditional git commands.

It's not a replacement for git, its to interact with the GitHub UI over the command line. There are 3 main commands from the CLI you can issue: gh CORE COMMANDS issue: Create and view issues pr: Create, view, and checkout pull requests repo: Create, clone, fork, and view repositories I still use the git cli and the github UI, but sometimes just view open PR's from the my terminal if I'm already in there.

Honestly the doc make it pretty unclear.

Some commands seem to be purely github related, which make sense, some others seem to overlap with just plain git.

> Clone the repository you want to work with using gh repo clone owner/repo

Like, what does this do apart from a regular git clone? Why is this necessary? I guess it additionally stores some meta information so that other "gh" commands know which repo they are on. This should have been a separate command IMHO to leave the regular git clone alone. Something like "git clone ssh://github.com/foo/bar" followed by "gh init foo/bar".

> When you’ve finished adding that feature or fixing that bug, use gh pr create

Same goes here. Why overlaying git commands? I would have expected to just push my branch, and then call something like "gh pr create "

> And your teammate can check out your pull request using gh pr checkout 1337

Same remark again and again, what does that do apart from checking out a branch? Why the overlay?

> view the diff with gh pr diff

So what's wrong with "git diff .."

> gh pr merge

Come on.. "git co ; git merge " needs to be overplayed?

> gh release create [tag name]

Oh sure, let's overlay git flow as well.

I mean overall the tool looks cute and all, but magic overlays is a no no for me.

Re: GitHub CLI 1.0

#43

Post by GormHouj »

azangru wrote: post #38
whoisjuan wrote: post #34

Earlier quoted context omitted.

Without a CLI you can't automate. (I guess you could, but it will be a pain in the ass)

Huh? Github actions have been around for over a year, and Github webhooks since I can't remember when.

Yeah, and this is the correct way to automate anything relating to github. Their API is insane.

Re: GitHub CLI 1.0

#44

Post by ape4 »

dberg wrote: post #2

Is this proof that regular git commands are too difficult to use? I also wonder what this is going to do for folks not using Github as now CLI users are going to "unlearn" all their traditional git commands.

Yeah, I wonder if `git` could be improved based on this.

Re: GitHub CLI 1.0

#45

Post by hjdarnel »

GormHouj wrote: post #43
azangru wrote: post #38

Earlier quoted context omitted.

Huh? Github actions have been around for over a year, and Github webhooks since I can't remember when.

Yeah, and this is the correct way to automate anything relating to github. Their API is insane.

...unless you use their CLI wrapper over the API (as in this post) :)

Re: GitHub CLI 1.0

#46

Post by mumblerino »

kkapelon wrote: post #12

What about https://hub.github.com/ ?

For the time being, hub still mostly helps with git operations, in fact it can be used as a git wrapper/replacement since it supports all of git’s commands.

gh on the other hand seems to very specifically work on GitHub’s non-git features, like Issues, PRs, repositories.

Re: GitHub CLI 1.0

#47

Post by Pandabob »

jkubicek wrote: post #39
shaky wrote: post #6

I don't understand the appeal of using a cli to manage commits, branches, remotes, merges with conflicts, and so on. To me all these things are so much better internalized and understood when presented visually. Git GUIs are aplenty (Sublime Merge being my latest discovery, SourceTree before that) and generally really good. Combined with the already amazing GitHub web GUI, it's a wonder what use case is better served…

It's worth installing the CLI just for a single command: `gh pr create --web` Saves me having to push my current branch, navigate to the repo page, hit the "create PR" button, etc.

Thanks for this, will start using it.

Re: GitHub CLI 1.0

#48

Post by [deleted] »

joppy wrote: post #29
afarrell wrote: post #11

Earlier quoted context omitted.

> better... understood when presented visually Often true for me as well. I like `tig`. > What use case is better served by sticking to the cli? Good question. Knowing the "why" of things is important. My answers: 1. Focus - Opening a browser and clicking around takes more patience. It tempts me to go update my company's internal documentation about something irrelevant to my current task. A CLI lets you pipe things…

1. Can be addressed by using a GUI which is not on the internet, for example SourceTree, the git interface in IntelliJ, probably many more. 2. Is often unimportant if the GUI tool can make common workflows one or two clicks. 3. Having the CLI tools to automate stuff is great, but is not necessarily the best way to have an interactive session with a repository. Some of the things I like about graphical interfaces for…

[deleted]

Re: GitHub CLI 1.0

#49

Post by Shared404 »

Is there an advantage to using this over the standard git cli tool?

It seems kinda like making a cli tool for a web interface for a tool. I guess I'm just missing something.

Edit: Spelling.

Post reply on HN