Live data from Hacker News

GitHub CLI 1.0

github.blog

181–190 of 221 posts

Re: GitHub CLI 1.0

#181

Earlier quoted context omitted.

I'll admit that the only time I heard of the GitHub CLI was last week when I thought to myself "it's really annoying going to the website every time I just want to push a new repo"

I use the older `hub` for only one command, but it's not that one! Instead, I use it for opening a PR from the command line. Since my work generally consists of making feature branches and PR'ing them, I use `hub pull-request` sometimes multiple times a day. Huge time saver.

Ah, but now you can `gh pr create` instead! Saves four keystrokes.

But by the way, `hub browse` and `hub sync` are handy too.

Re: GitHub CLI 1.0

#182
post #76

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.

Yes, you are missing. This is GitHUB cli, not git cli. This has nothing to do with git.

> GitHUB cli

So a wrapper for an API for a website for git? Why?

Edit: Also, how does anything working with GitHub have nothing to do with git?

Edit 2: Don't get me wrong, this looks like a cool tool. I'm just curious about the motivation.

Re: GitHub CLI 1.0

#184

Earlier quoted context omitted.

CLI or not, it's centralized/siloed all the same. I'm sticking to Git.

It would be really nice if the other features of github could get into the decentralized model of git... I could imagine issues and PR reviews/comments all being mini-commits to some kind of parallel metadata repo under the hood for example.

There are some experimental tools for distributed code review and issues.

https://github.com/google/git-appraise

https://github.com/dspinellis/git-issue

Would be nice to have something more polished though.

Re: GitHub CLI 1.0

#185

Wonder if this would lead to the end of hub https://hub.github.com >.

They do not treat hub as an official github project and rather an unofficial open source project that they don't plan to do away with They have a document where they expand on this: https://github.com/cli/cli/blob/trunk/docs/gh-vs-hub.md

To highlight from that doc:

"The GitHub CLI team is focused solely on building out the new tool, gh. We aren’t shutting down hub or doing anything to change it. It’s an open source project and will continue to exist as long as it’s maintained and keeps receiving contributions."

Re: GitHub CLI 1.0

#186

GitHub is killing it with these features. I wonder how long Azure Repos will survive on it's own.

And Golang is killing it for these kind of applications.

I was wondering if this was written in Go, and specifically using the Cobra framework. I checked out the repo and it was!

Other common CLIs written with the same framework: kubectl, hugo, rclone (to name a few)

Really is a great option.

Re: GitHub CLI 1.0

#187

Earlier quoted context omitted.

CLI or not, it's centralized/siloed all the same. I'm sticking to Git.

It would be really nice if the other features of github could get into the decentralized model of git... I could imagine issues and PR reviews/comments all being mini-commits to some kind of parallel metadata repo under the hood for example.

Have a look at fossil https://fossil-scm.org/home/doc/trunk/www/index.wiki

Or maybe git-appraise https://github.com/google/git-appraise git-bug https://github.com/MichaelMure/git-bug

And recently discussed here https://radicle.xyz/

Re: GitHub CLI 1.0

#190
post #189

Does something like this exist for bitbucket too?

I’d be surprised if bitbucket’s dev tooling budget was 1/10th of GitHub’s even before the MS acquisition.

Working with BB APIs has not been fun at any point in the past 5 years or so :(

Post reply on HN