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

191–200 of 221 posts

Re: GitHub CLI 1.0

#191

Post by brundolf »

trilinearnz wrote: post #179
yakubin wrote: post #106

Earlier quoted context omitted.

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

Good point. It never seemed like the distributed "selling point" of Git (and Mercurial et al) really caught on. I remember trying to extoll it's virtues to our team at the time (pre-Github). No one source of truth as such, just everyone swapping changes as needed. It's kind of ironic that Git's most popular incarnation is based upon a centralised model. Is it just a case of the distributed workflow just not being tha…

I think in practice it's most useful as a recovery feature. I once got locked out of my Bitbucket account and had to recover a repo, which I'd been paid to develop, from Heroku of all places. I was extremely grateful at that point that all git repos are complete mirrors of each other.

Re: GitHub CLI 1.0

#192

Post by jrochkind1 »

wlonkly wrote: post #181
jrochkind1 wrote: post #153

Earlier quoted context omitted.

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.

It's all the same to me if it works, it's easy to switch the one command I use, I'll probably switch to `gh pr create`, since it appears to be the more maintained package. `hub pull-request` does a few things that annoy me or that seem buggy, maybe I'll compare to `pr`.

I never did use `hub` as a "wrapper" for `git`, I've always typed `hub pull-request`. I never liked the wrapper idea. So I approve of `gh` abandoning it.

Re: GitHub CLI 1.0

#193

Post by hemanta212 »

Shared404 wrote: post #182
pbalau wrote: post #76

Earlier quoted context omitted.

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.

Github provides additional functionalities over git for which users had to switch from cli to web. Now they are bringing those additional functionalities to cli so users dont have to switch context

Re: GitHub CLI 1.0

#194

Post by cptskippy »

alkonaut wrote: post #177
cptskippy wrote: post #128

Earlier quoted context omitted.

We did some training with Microsoft last fall and the coordinator straight up told us that DevOps functionality was being duplicated in Github and that DevOps was being sunset eventually. He recommended using YAML for all Pipeline Development as they were trying very hard to ensure that it would be compatible but legacy pipelines would not.

Azure Repos and maybe Pipelines be sunset and replaced by GiHub equivalents, but they’d have a hard time sunsetting the task management (Boards) without first significantly expanding it in Github. Many swear by their hierarchical backlogs, custom column Kanban boards and complex reporting. GitHub issues is extremely simple in comparison.

They're rolling Planner and Tasks into Teams, I fear they may try to substitute that and Power Bi for DevOps Boards.

Re: GitHub CLI 1.0

#197

Post by Shared404 »

hemanta212 wrote: post #193
Shared404 wrote: post #182

Earlier quoted context omitted.

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

Github provides additional functionalities over git for which users had to switch from cli to web. Now they are bringing those additional functionalities to cli so users dont have to switch context

Ah, that makes sense then. Many thanks.

Re: GitHub CLI 1.0

#198

Post by rendall »

dheera wrote: post #176
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

This is awesome, but with all due respect I also wish git itself was also improved. Goddamn merge commits, and always have to go googling "oh shit how do I erase the last commit" when I accidentally commit to master. It should at least spit out a warning if you created a branch and then try to commit to master. Git lfs and git-crypt should be a feature of the main product and not plugins. Files over a certain size sh…

There are "hooks" in git that can be used to modify its behavior, to e.g. "spit out a warning if you created a branch and then try to commit to master"

This seems to be a good resource https://githooks.com/

Re: GitHub CLI 1.0

#199

Post by petepete »

DonCopal wrote: post #180

Can you also browse the code with this? Find a file? Find only within xml files? Copy a link to a specific line? Create gists?

You can create, edit, list and view gists. You can't copy a link to a specific line (afaik). As you run this tool from your project directory you can browse and search code using your tools of choice.

It's an excellent tool even if you just use it to quickly create and view PRs and issues, as I do.

Re: GitHub CLI 1.0

#200

Post by [deleted] »

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…

[deleted]
Post reply on HN