Live data from Hacker News

GitHub CLI 1.0

github.blog

11–20 of 221 posts

Re: GitHub CLI 1.0

#11
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…

> 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 to grep which lets you focus on specific information you care about.

2. Memory - I can write aliases to help me remember my common workflows.

3. Automation - I can have a script check PRs for me. This reduces context switching and enables greater focus and productivity.

Re: GitHub CLI 1.0

#13
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…

Better scripting / automation maybe? I don't have any specific example in mind right now, but being able to pipe things together with other utilities could make for interesting applications, and is easier than having to interact with a REST API.

Re: GitHub CLI 1.0

#15
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.

How you could create issue with git? Project on github is much more that just git repo

Re: GitHub CLI 1.0

#16
Oh wow this is great. I’ve been wanting an org mode integration with GitHub for a while, and this tool might make it easy enough for me to hack together this weekend.

Basically I want to be able to pull up a buffer with a list of issues assigned to me and copy them into my org mode todo list

Re: GitHub CLI 1.0

#17
post #13
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…

Better scripting / automation maybe? I don't have any specific example in mind right now, but being able to pipe things together with other utilities could make for interesting applications, and is easier than having to interact with a REST API.

Yeah, CI solutions can use this command instead of having to write and maintain their own github API interfacing, for example.

Re: GitHub CLI 1.0

#18
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…

> 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…

Speed and overhead are both areas that should get a lot more focus nowadays; the Github desktop app along with a ton of other applications are Electron / webapps, each one adding a number of always-active processes, complex and expensive rendering, script execution, and a ton of memory usage, which do add up over time. I mean a lot of developers will have two or three Electron apps open right now; Slack and / or Discord, VS Code, Notion, and a bunch more in their browser of choice.

Re: GitHub CLI 1.0

#19
post #16

Oh wow this is great. I’ve been wanting an org mode integration with GitHub for a while, and this tool might make it easy enough for me to hack together this weekend. Basically I want to be able to pull up a buffer with a list of issues assigned to me and copy them into my org mode todo list

You can do this using Forge within Magit already! And it also works for Gitlab: https://magit.vc/manual/forge/

Re: GitHub CLI 1.0

#20
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…

If you are not on Linux, please try Fork. It's plenty fast and very robust, I have fallen in love with it on first sight.
Post reply on HN