Live data from Hacker News

GitHub CLI 1.0

github.blog

211–220 of 221 posts

Re: GitHub CLI 1.0

#211

Earlier quoted context omitted.

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

Farther along in same doc:

"hub is a project whose maintainer also happens to be a GitHub employee. He chooses to maintain hub in his spare time, as many of our employees do with open source projects."

My experience at FANMAG has been that "spare time" is the scarcest of all resources.

Re: GitHub CLI 1.0

#212

Earlier quoted context omitted.

Consider donating -- if you're a software engineer, acknowledge the value of your own time!

I donate little bits here and there when I can, but I'm unfortunately not in financial position to give what I think the maintainers deserve. Instead I try to submit documentation patches to projects whenever I find myself digging through the source code trying to answer a question the docs didn't make clear.

That makes you a solid contributor in my book!

Re: GitHub CLI 1.0

#213
post #210

Earlier quoted context omitted.

"A pre-push hook that prevents direct code push to master branch" and I would want "spit out a warning if you created a branch and then try to commit to master" Sometimes I would want to commit to master, I want an overridable warning iff I just created branch.

How about #!/bin/sh BRANCHES_POINTING_TO_HEAD=$(git branch --contains HEAD |wc -l) CURRENT_BRANCH=$(git branch --show-current) if [ "$BRANCHES_POINTING_TO_HEAD" -gt 1 ]; then if [ "$CURRENT_BRANCH" = "master" ]; then echo "You're committing to master even though other branches exist." echo "override with git commit --no-verify" exit 1 fi fi You'll need git 2.22 for the --show-current git option. But also I would sugg…

A better UX would be

    $ git checkout 
     doesn't exist. Would you like to create it (Y/n):
The real problem with "git" is just way too many options. For automated tools there can be a "-n" non-interactive option that fails with an error code and doesn't ask questions.

Re: GitHub CLI 1.0

#214
post #156

Great news but my first thought was that it's hard enough for juniors to grasp the difference between git and github. Now they will be even more confused... :]

To be fair, they’re not explicitly saying to alias it as `git` this time. At least with a different name the distinction is clearer

I have never really grokked the concept of git to push or pull, commit or diff the code that I write. Tried to convince myself a few times that is best practise from the industry. I still tgz my source code before I intend to make substantial change.

Github for me is simply a repo of open source code that I can inspect before I use someone else library.

Re: GitHub CLI 1.0

#215

Earlier quoted context omitted.

To be fair, they’re not explicitly saying to alias it as `git` this time. At least with a different name the distinction is clearer

I have never really grokked the concept of git to push or pull, commit or diff the code that I write. Tried to convince myself a few times that is best practise from the industry. I still tgz my source code before I intend to make substantial change. Github for me is simply a repo of open source code that I can inspect before I use someone else library.

Source control is well worth the learning curve. Git is harder to learn than most, though. I hear Mercurial is easier to learn; maybe give it a try?

Re: GitHub CLI 1.0

#216
post #215

Earlier quoted context omitted.

I have never really grokked the concept of git to push or pull, commit or diff the code that I write. Tried to convince myself a few times that is best practise from the industry. I still tgz my source code before I intend to make substantial change. Github for me is simply a repo of open source code that I can inspect before I use someone else library.

Source control is well worth the learning curve. Git is harder to learn than most, though. I hear Mercurial is easier to learn; maybe give it a try?

[deleted]

Re: GitHub CLI 1.0

#217
post #132

Earlier quoted context omitted.

I find projectile too chatty and distracting none thing I like about emacs is that I can focus on what I’m working on.

In what way do you find it too chatty? That hasn't been my experience, but I do use a pretty small subset of it. Are you using it on its own, or with helm/ivy?

It could have been hel or ivy I was seeing. I don’t like the mode line moving (growing the minibuffer) as I typically keep my eyes on part of the buffer and don’t want anything moving (or worse, obscuring where I’m looking)

Re: GitHub CLI 1.0

#218
post #134

Earlier quoted context omitted.

How do you know the difference between being in an EEE scenario versus just being in a scenario where people keep working on their product?

When the open components that allow free interoperability with GitHub's competitors are replaced with proprietary components that don't.

Did that happen?

Re: GitHub CLI 1.0

#219
post #134

Earlier quoted context omitted.

How do you know the difference between being in an EEE scenario versus just being in a scenario where people keep working on their product?

Just look at history.

Does that mean it _always_ happens? Or only sometimes?

Re: GitHub CLI 1.0

#220
post #215

Earlier quoted context omitted.

I have never really grokked the concept of git to push or pull, commit or diff the code that I write. Tried to convince myself a few times that is best practise from the industry. I still tgz my source code before I intend to make substantial change. Github for me is simply a repo of open source code that I can inspect before I use someone else library.

Source control is well worth the learning curve. Git is harder to learn than most, though. I hear Mercurial is easier to learn; maybe give it a try?

Isn’t mercurial pretty much dead? I know Bitbucket dropped support for it last year. I’ve also found it no more intuitive than git personally.
Post reply on HN