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

51–60 of 221 posts

Re: GitHub CLI 1.0

#51

Post by Aperocky »

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…

cli should be the basis of everything.

There can be UI and sometime that's helpful, but all action contained therein will be available on cli, just because that's exactly what the UI calls.

Re: GitHub CLI 1.0

#52

Post by grugagag »

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…

Scripting and shortcuts are very useful. To each their own but doing repetitive tasks in a GUI is prone to errors and boredom

Re: GitHub CLI 1.0

#53

Post by jillesvangurp »

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.

Yes, that's what I do as well. I also have the old hub frontend for git installed. The idea is that you simply alias git to hub and then you get a few extra commands.

My favorite is "git browse", which opens a browser for the current repo & branch. There are a few other commands that are probably useful but that I don't really do much with.

Re: GitHub CLI 1.0

#54

Post by whoisjuan »

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.

Not really sure what you're talking about. Not everything you automate on GitHub happens in the context of a CI pipeline like in GitHub Actions. There are many cases for small scripts where you just need to execute a couple of commands.

Re: GitHub CLI 1.0

#56

Post by httpsterio »

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…

a CLI is scriptable and automateable, so there's that at least. How about "find all related issues and close based on the commit message and push to production if it's an urgent fix" etc

Re: GitHub CLI 1.0

#58

Post by djsumdog »

I've used ghi before just for issues:

https://github.com/stephencelis/ghi

It's pretty nice. I like seeing these features supported officially (I think hub supported many of these unofficially for years).

What tools are there like this for Gitlab? I remember struggling just to find a decent CLI for their issue tracker.

All my new stuff is on Gitlab and I prefer Gitlab since if I ever want to, I can always just management my own instance and migrate to it. No such options with Github.

Re: GitHub CLI 1.0

#59

Post by dvlsg »

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.

That is pretty nice.

I've been doing `git push -u origin HEAD` and then using my mouse to click on the "go here to create a PR" link that gets printed, which isn't too bad. Takes you right to the page where you can review the changeset before opening the PR. If I'm not actually ready to open a PR by the time I push upstream, I just open a draft instead.

Post reply on HN