Which Github interface?


Doug Lee
 

For those who manage add-ons via Github and/or use Github in other contexts:

Do you find the web interface best, or the Desktop app (I'm looking at version 3.2.0), or GitCLI and Git
itself, all from command lines?

I ask because I am now working with a client who uses Github in an Enterprise setup, which appears at a glance
to complicate things like cloning branches from a command line; and the client is trying to use the Desktop
app instead of the web interface. I had failed to notice that there was a Desktop app.


--
Doug Lee dgl@... http://www.dlee.org
"I am a leader by default, only because nature does not allow a vacuum."
Bishop Desmond Tutu


 

Hi,
I use GitHub web interface and use Git command-line for Git related tasks.
Cheers,
Joseph

-----Original Message-----
From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io>
On Behalf Of Doug Lee
Sent: Wednesday, March 22, 2023 12:07 PM
To: nvda-addons@nvda-addons.groups.io
Subject: [nvda-addons] Which Github interface?

For those who manage add-ons via Github and/or use Github in other contexts:

Do you find the web interface best, or the Desktop app (I'm looking at
version 3.2.0), or GitCLI and Git itself, all from command lines?

I ask because I am now working with a client who uses Github in an
Enterprise setup, which appears at a glance to complicate things like
cloning branches from a command line; and the client is trying to use the
Desktop app instead of the web interface. I had failed to notice that there
was a Desktop app.


--
Doug Lee dgl@... http://www.dlee.org
"I am a leader by default, only because nature does not allow a vacuum."
Bishop Desmond Tutu


Alberto Buffolino
 

Joseph Lee, il 22/3/2023, ha scritto:
I use GitHub web interface and use Git command-line for Git related tasks.
Alberto:
even gh, that is, github-cli, is a great tool in addition to git, and it can open the correct web page if browser is sometime preferable.
For example, I discovered recently that if I have a branch where I made a PR from, I can run:
gh pr view -w
to open in browser the PR info/discussion page.
Alberto


Noelia Ruiz
 

Also, to run GitHub Actions, GH CLI is great, or to create pull
requests without using the browser or using it.
I like a lot GitHub CLI in addition to Git and I'd recommend it.

2023-03-22 20:42 GMT+01:00, Alberto Buffolino <a.buffolino@...>:

Joseph Lee, il 22/3/2023, ha scritto:
I use GitHub web interface and use Git command-line for Git related
tasks.
Alberto:
even gh, that is, github-cli, is a great tool in addition to git, and it
can open the correct web page if browser is sometime preferable.
For example, I discovered recently that if I have a branch where I made
a PR from, I can run:
gh pr view -w
to open in browser the PR info/discussion page.
Alberto






Luke Davis
 

Doug Lee wrote:

For those who manage add-ons via Github and/or use Github in other contexts:
Do you find the web interface best, or the Desktop app (I'm looking at version 3.2.0), or GitCLI and Git
itself, all from command lines?
In my opinion the desktop app is junk. When I tried it in 2021 or early 2022, it had no accessibility advantage over the website, and seemed mostly to be a clunky wrapper around git commandline, with some hooks to the website.

On a daily basis I use git and the gh interface to the GitHub API, as my primary tools. I often use the GitHub website for issue management when email is insufficient, and it's good for account management and line by line commenting on pull requests. Otherwise I try to stick to gh and git whenever possible.

That said, I'm very comfortable with the commandline, and have a good memory for commands and options, or know where to find them fast when I need them. The GitHub website is actually pretty good, and if the commandline isn't your thing, it is a fine option. Though if I had to use it regularly for committing, git log viewing, branching/rebasing and other gitish functions, it would drive me crazy, just because of how much more efficient the CLI is for that sort of thing.

Luke


Luke Davis
 

Doug Lee wrote:

to complicate things like cloning branches from a command line
Maybe because he's trying to clone branches? :)
One does not clone branches.
One clones repos.
Branches are checked out.

Cloning:

git clone ssh://github.com/owner/repo
# Or:
gh repo clone owner/repo

To checkout a branch:

cd repo
git checkout branch

I don't know what particular problems your client is having, but from what I've read, from a git prospective the enterprise server shouldn't be any different.

This might help:

https://docs.github.com/en/enterprise-server@3.5/admin/configuration/configuring-your-enterprise/command-line-utilities

Luke


Doug Lee
 

Luke, you asked in a subsequent message (that I lost accidentally) whether my client was trying to clone a
branch instead of a repo. Minutes after I sent my message here, I realized I had typed the wrong word. He was
creating a branch, but the people on that call informed me that using the command line is tricky for that
because some setup is required to be able to make a branch from an existing repo within the enterprise. The
two factors I remember being mentioned were named repositories and authorization processes.

On Wed, Mar 22, 2023 at 05:52:15PM -0400, Luke Davis wrote:
Doug Lee wrote:

For those who manage add-ons via Github and/or use Github in other contexts:
Do you find the web interface best, or the Desktop app (I'm looking at version 3.2.0), or GitCLI and Git
itself, all from command lines?
In my opinion the desktop app is junk. When I tried it in 2021 or early 2022,
it had no accessibility advantage over the website, and seemed mostly to be a
clunky wrapper around git commandline, with some hooks to the website.

On a daily basis I use git and the gh interface to the GitHub API, as my
primary tools. I often use the GitHub website for issue management when email
is insufficient, and it's good for account management and line by line
commenting on pull requests. Otherwise I try to stick to gh and git whenever
possible.

That said, I'm very comfortable with the commandline, and have a good memory
for commands and options, or know where to find them fast when I need them.
The GitHub website is actually pretty good, and if the commandline isn't your
thing, it is a fine option. Though if I had to use it regularly for
committing, git log viewing, branching/rebasing and other gitish functions, it
would drive me crazy, just because of how much more efficient the CLI is for
that sort of thing.

Luke


--
Doug Lee dgl@... http://www.dlee.org
"It's not easy to be crafty and winsome at the same time, and few accomplish
it after the age of six." --John W. Gardner and Francesca Gardner Reese