Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Git password authentication is shutting down

github.blog

Post reply on HN
Print view View original

121–130 of 353 posts

Re: Git password authentication is shutting down

#121

Post by pier25 »

morpheuskafka wrote: post #116
hiimshort wrote: post #24

I'm fine with this change for my usage, I don't think I've used password auth for myself or any automated service I've setup for years now. However, this will introduce more confusion for newcomers who already have to figure out what Git, GitHub, etc are. I just spent some time last weeekend teaching someone the basics of how to create a new project. Such a simple idea required introducing the terminal, basic termina…

GitHub Desktop, since being rewritten whenever the last time was, is pretty decent and I just have people install that to initially clone the project and set up the remotes and then they can still use the command line or IDE to make commits and pushes if they want.

This.

It also has an undo button to undo the last commit which has saved my ass a couple of times.

Re: Git password authentication is shutting down

#122

Post by spydum »

Animats wrote: post #79
hiimshort wrote: post #24

I'm fine with this change for my usage, I don't think I've used password auth for myself or any automated service I've setup for years now. However, this will introduce more confusion for newcomers who already have to figure out what Git, GitHub, etc are. I just spent some time last weeekend teaching someone the basics of how to create a new project. Such a simple idea required introducing the terminal, basic termina…

Setting up this authentication is a huge pain. First, the Github site lies to you. It tells me that, having previously generated a token, that token has never been used. It's been in use for months on one machine. Their web site and their repository system are not talking to each other. Then they want you to generate a new token, in the "new format". Then they refuse to generate a token valid for more than a year. Wi…

to be fair ms azure has a nice login experience for their cli tool (imho anyways).

Re: Git password authentication is shutting down

#123

Post by berdon »

pier25 wrote: post #121
morpheuskafka wrote: post #116

Earlier quoted context omitted.

GitHub Desktop, since being rewritten whenever the last time was, is pretty decent and I just have people install that to initially clone the project and set up the remotes and then they can still use the command line or IDE to make commits and pushes if they want.

This. It also has an undo button to undo the last commit which has saved my ass a couple of times.

You could just use ‘git undo’ or ‘git reset —-soft HEAD~1’.

Re: Git password authentication is shutting down

#124

Post by chaorace »

cstrat wrote: post #100
pjc50 wrote: post #48

Earlier quoted context omitted.

The solution that everyone actually uses until they learn the unnecessary details is "take a backup of relevant files and blow away & redownload the repo".

wait there is another way?

    git stash
    git reset --hard master
    git pull
    git stash pop

Re: Git password authentication is shutting down

#125

Post by bostonsre »

cxr wrote: post #119
post-it wrote: post #53

Earlier quoted context omitted.

> Think, having your graphics designer able to make commits, or having someone who only wants to update docs. GitHub's web interface is pretty good for this.

Not really. People say stuff like this, but what they're really talking about is their own familiarity with GitHub (in the vein of http://lighttable.com/2014/05/16/pain-we-forgot/ >). What GitHub has going for it is that it is familiar to ("a majority of"?) working developers, and that it's better than both the competition and the Git CLI itself, but from a reality-adjusted perspective, GitHub is pretty bad, too. (Th…

I mean you could have stuff that requires prs, but you could just use the ui pretty much like a wiki.

1. Go to dev branch

2. Find file and edit it

3. Commit change

Re: Git password authentication is shutting down

#126

Post by javajosh »

cxr wrote: post #119
post-it wrote: post #53

Earlier quoted context omitted.

> Think, having your graphics designer able to make commits, or having someone who only wants to update docs. GitHub's web interface is pretty good for this.

Not really. People say stuff like this, but what they're really talking about is their own familiarity with GitHub (in the vein of http://lighttable.com/2014/05/16/pain-we-forgot/ >). What GitHub has going for it is that it is familiar to ("a majority of"?) working developers, and that it's better than both the competition and the Git CLI itself, but from a reality-adjusted perspective, GitHub is pretty bad, too. (Th…

Interestingly, Microsoft has a product called TFS that has a great wiki implementation: it's native markdown (with github enhancements), a decent in-browser editor/viewer, and it's backed by git. Plus it has some nice features that let you refer to people with the at-symbol (@) and work items (bugs, tasks, stories, features, etc) with a hash symbol (#), and some other stuff. Github itself has some of these features; I'm not aware of anything else like it (Tiddlywiki, ignoring it's unusual runtime, may be the closest that I'm aware of).

Re: Git password authentication is shutting down

#127

Post by javajosh »

berdon wrote: post #123
pier25 wrote: post #121

Earlier quoted context omitted.

This. It also has an undo button to undo the last commit which has saved my ass a couple of times.

You could just use ‘git undo’ or ‘git reset —-soft HEAD~1’.

Isn't "git undo" a very recent invention? In my experience, people don't upgrade git very often. As for your other comment, see the xkcd reference elsewhere in this thread :)

Re: Git password authentication is shutting down

#128

Post by DangitBobby »

chaorace wrote: post #124
cstrat wrote: post #100

Earlier quoted context omitted.

wait there is another way?

git stash git reset --hard master git pull git stash pop

Uh oh, you've now merged remote master into your local master which was two commits ahead and 3 behind!

My git config has fast-forward only for pulls and I habitually use --ff-only for any pull :)

Re: Git password authentication is shutting down

#129

Post by runnerup »

outworlder wrote: post #43
hiimshort wrote: post #24

I'm fine with this change for my usage, I don't think I've used password auth for myself or any automated service I've setup for years now. However, this will introduce more confusion for newcomers who already have to figure out what Git, GitHub, etc are. I just spent some time last weeekend teaching someone the basics of how to create a new project. Such a simple idea required introducing the terminal, basic termina…

> How can we offer a more gentle learning curve for budding developers while still requiring "real" projects to use best practices for security and development Difficult question. In the past, the solution was just not to use any of that. A bunch of files inside a random folder in your computer that were not version controlled in any way. That worked, but that's also the reason I lost most of the source code that I'v…

> In the past, the solution was just not to use any of that. A bunch of files inside a random folder in your computer

This is what my company does. Except we use git. Everyone just keeps their repo on their drive and there's no central "canonical" repository. Everyone has a personal folder in the main fileserver and they push frequently to their personal remote repo.

Any time they send emails saying they've made a notable milestone, anyone curious just merges against their remote.

The codebases somehow rarely (never) diverge catastrophically. Maybe because we're doing embedded work.

Post reply on HN