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

81–90 of 221 posts

Re: GitHub CLI 1.0

#81

Post by algorithmsRcool »

georgedrummond wrote: post #7
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.

No doubt the intent of this tool is to tightly couple your development flow to GitHub/Microsoft. Makes switching to other vendors more painful further down the line.

I don't understand this mentality. Git itself doesn't provide a way to interact with PRs or issues on GitHub.

This utility does.

If you are uncomfortable with using GH to manage issues and PRs you shouldn't probably shouldn't be using GH.

Re: GitHub CLI 1.0

#82

Post by chungus »

DvdMgr wrote: post #19
mroll wrote: 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/

Been meaning to try Forge, thanks for the reminder. Honestly, Magit alone is enough reason to use Emacs. Projectile is a close second for me.

Re: GitHub CLI 1.0

#85

Post by clon »

All of GH improvements have become irrelevant for me since they vanished one of our repos. No notification, no warning, no recourse. Just gonsky. It was just a simple library we wrote to talk to a public IP2Country REST service. Pushed to GitLab, end of.

Re: GitHub CLI 1.0

#86

Post by munchbunny »

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 more about automation than about end-user (developer) UI. CLI gives you a simple way to automate tooling for your team's processes (simpler than writing code to call into REST API's), and it's code, so you can maintain it as code and not some set of configurations on a UI somewhere.

Re: GitHub CLI 1.0

#88

Post by mikepurvis »

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.

Yeah this is huge— I used to use `hub` for this one thing as well. The alternative is even worse if you cloned from a repo you don't have push access to, so your first step is going to the web UI, creating the fork, switching the remote on your clone, and then _finally_ pushing and creating the PR.

Re: GitHub CLI 1.0

#89

Post by steveklabnik »

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.

These days when I push a branch, github gives a URL in the response that I can click from the terminal to open a PR. It is indeed very good.

Re: GitHub CLI 1.0

#90

Post by juped »

swagonomixxx wrote: post #68
juped wrote: post #65

Earlier quoted context omitted.

What's amazing about the Github web GUI?

It's not utter garbage (at least not yet).

I'm not sure this is the case! In fact, I strongly suspect that its inability to display logs or diffs correctly has contributed to the widespread developer confusion with respect to Git, especially since there are many people out there who think, implicitly if not explicitly, that Git and Github are one and the same.

You know how a lot of people think merge commits (an important keystone in how easy Git makes it to read and write meaningful history) are inherently "confusing" or "messy", and try to avoid creating them? Well, if you look at them in Github's awful log interface, they sort of are! This doesn't seem like the fault of those developers, and it's not Git's fault, since it ships with powerful command-line and GUI tools for making sense of things.

Post reply on HN