GitHub CLI 1.0

#1

Post by todsacerdoti » Thu, Sep 17, 2020, 1:03 PM UTC

Re: GitHub CLI 1.0

#2

Post by dberg » Thu, Sep 17, 2020, 1:34 PM UTC

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.

Re: GitHub CLI 1.0

#3

Post by rolfvandekrol » Thu, Sep 17, 2020, 1:36 PM UTC

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.

It seems like this is not a CLI for git, but for the Github specific stuff, such as issues and pull requests.

Re: GitHub CLI 1.0

#4

Post by pbalau » Thu, Sep 17, 2020, 1:37 PM UTC

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, is a complement. See [0]. Basically allows doing from cli things you could only do from the UI before (without writing your custom scripts).

[0] https://cli.github.com/manual/index

Re: GitHub CLI 1.0

#5

Post by cfors » Thu, Sep 17, 2020, 1:38 PM UTC

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.

It's not a replacement for git, its to interact with the GitHub UI over the command line.

There are 3 main commands from the CLI you can issue:

  gh

  CORE COMMANDS

   issue:      Create and view issues
   pr:         Create, view, and checkout pull requests
   repo:       Create, clone, fork, and view repositories

I still use the git cli and the github UI, but sometimes just view open PR's from the my terminal if I'm already in there.

Re: GitHub CLI 1.0

#6

Post by shaky » Thu, Sep 17, 2020, 1:42 PM UTC

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 by sticking to the cli, other than this misplaced notion that it's what the cool kids are doing.

Re: GitHub CLI 1.0

#7

Post by georgedrummond » Thu, Sep 17, 2020, 1:44 PM UTC

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.

Re: GitHub CLI 1.0

#8

Post by adriancooney » Thu, Sep 17, 2020, 1:46 PM UTC

I love this tool and use it everyday. Thank you Github and contributors.

Re: GitHub CLI 1.0

#9

Post by judofyr » Thu, Sep 17, 2020, 1:46 PM UTC

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…

There are a bunch of examples which I find very useful with the CLI: Creating new repos (gh repo create), opening the repo in the browser (gh repo view), checking out PRs when you have the ID (gh pr checkout ID), diffing the currently checkout PR against the base (gh pr diff).

Re: GitHub CLI 1.0

#10

Post by aosaigh » Thu, Sep 17, 2020, 1:47 PM UTC

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…

How about when you already do most of your development on the command line? In web development anyway, most frameworks, servers and tools are CLI only so you are already on the command line for the most part. It's far quicker to do a quick commit there and then rather then move to a GUI.

That said, I use both. Most of my commits etc. are on the CLI but I still switch to a GUI if I want to browse the repo or see more detailed diffs etc.