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

231–240 of 353 posts

Re: Git password authentication is shutting down

#231

Post by spockz »

BeefySwain wrote: post #39
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…

I also have found teaching someone how to be even marginally capable of contributing to a Github project from scratch to be a very time consuming and frustrating thing. Think, having your graphics designer able to make commits, or having someone who only wants to update docs. The worst part is the "easier" solutions are actually just footguns in disguise, as soon as they accidentally click the wrong thing and end up…

I suppose contributing is easier with the built-in vs code editor now? (Press `.` when logged in.)

The only thing lacking is public code spaces. I can’t even try them out without paying for GitHub Teams or GitHub Enterprise.

Re: Git password authentication is shutting down

#232

Post by oldsecondhand »

tmm84 wrote: post #147
francislavoie wrote: post #131

Earlier quoted context omitted.

I've successfully gotten non-devs to use Git via GitKraken. Its interface is simple, but doesn't hide anything. Harder to make mistakes because it actually shows you what's going on, and even has an "Undo" button which lets you back out of mistakes most of the time.

When I was just starting out with git and hadn't really learned enough of the more advanced workflows in git I really wanted gitkraken. Much like the jetbrains software it has a license requirement so that can be a turn-off but if you're trying to teach git in a visual way on teaching projects this software is great.

Sourcetree has a quite usable free version, I found it very useful as a beginner but haven't used it in the last 4 years.

Re: Git password authentication is shutting down

#233

Post by stinos »

spockz wrote: post #231
BeefySwain wrote: post #39

Earlier quoted context omitted.

I also have found teaching someone how to be even marginally capable of contributing to a Github project from scratch to be a very time consuming and frustrating thing. Think, having your graphics designer able to make commits, or having someone who only wants to update docs. The worst part is the "easier" solutions are actually just footguns in disguise, as soon as they accidentally click the wrong thing and end up…

I suppose contributing is easier with the built-in vs code editor now? (Press `.` when logged in.) The only thing lacking is public code spaces. I can’t even try them out without paying for GitHub Teams or GitHub Enterprise.

I suppose contributing is easier with the built-in vs code editor now? (Press `.` when logged in.)

Wow, never heard about this (ok I don't follow all possible tech news), but why is this not clearly advertised on github itself? Looks pretty neat and seems to work fine (for what it offers) as well.

Re: Git password authentication is shutting down

#235

Post by toastal »

echohack5 wrote: post #195
toastal wrote: post #192

Earlier quoted context omitted.

Why are we always teaching Git in the context of GitHub though? There HSA to be a simpler, more platform agnostic way.

Warning, snarky opinion ahead: because git has terrible cli operations that only make sense to people who under reflog and rebase and the underpinnings of git as opposed to any sort of file-based operations, which is how most people understand computers. Github looks and behaves like a filesystem with a timeline, which is not accurate to how git works functionally, but that's what makes sense to most people out of th…

Sure, but churning out students on a singular, closed-source, megacorp-owned platform isn't the right thing to do either.

Re: Git password authentication is shutting down

#236

Post by jampekka »

WorldMaker wrote: post #109
jampekka wrote: post #90

So now I can't use git client on github repos anymore without carrying a device that has some impossible to memorize key or token on it? I hate it. I don't care much for the slight chance that someone gets into my github account. I care a lot more that now I have to jump hoops to get into my account myself. There's more to things than security.

You can use Access Tokens which are "application specific" passwords instead of SSH keys. You can use a git credential manager such as GCM Core ( https://github.com/microsoft/Git-Credential-Manager-Core ) to automate the flow from username/password to access token. (It pops up a browser window where you login, retrieves and access token for you.)

Sounds a lot like a hoop. With password I can use any device with git installed to pull and push from/to github repos. Now I'd need a hack like this on top.

I prefer less tools to more tools. Probably a losing battle given how the field is developing.

Re: Git password authentication is shutting down

#237

Post by shikoba »

DangitBobby wrote: post #197

Anyone else notice that GitHub recently removed the sample code for cloning with SSH?

I deleted my github account when M$ took over so I can't check. You're logged, you have declared a SSH key but they still don't provide the small code line to clone using SSH?

Re: Git password authentication is shutting down

#238

Post by csmpltn »

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…

> "Such a simple idea required introducing the terminal, basic terminal commands, GitHub, git and its most common commands. It took about 3 hours for us to get through just the most basic pieces."

I don't get this.

"Can you imagine? Learning to program a computer took us some hours!"

What do you expect? That people without prior knowledge or experience just pick up source control in seconds? I'm honestly wondering - what makes you think source control systems are so trivial? Is it really too much to ask a newcomer to invest some hours into learning something these days?

Re: Git password authentication is shutting down

#239

Post by caslon »

csmpltn wrote: post #238
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…

> "Such a simple idea required introducing the terminal, basic terminal commands, GitHub, git and its most common commands. It took about 3 hours for us to get through just the most basic pieces." I don't get this. "Can you imagine? Learning to program a computer took us some hours!" What do you expect? That people without prior knowledge or experience just pick up source control in seconds? I'm honestly wondering -…

...they are so trivial that they can be figured out in less than three hours. Mercurial can be learned in minutes. Fossil in half an hour. Even git isn't particularly difficult; you can get "working knowledge" of it by glancing at this:

https://git-send-email.io

Re: Git password authentication is shutting down

#240

Post by yunohn »

csmpltn wrote: post #238
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…

> "Such a simple idea required introducing the terminal, basic terminal commands, GitHub, git and its most common commands. It took about 3 hours for us to get through just the most basic pieces." I don't get this. "Can you imagine? Learning to program a computer took us some hours!" What do you expect? That people without prior knowledge or experience just pick up source control in seconds? I'm honestly wondering -…

> what makes you think source control systems are so trivial?

The commenter is referring to the tooling around git, wasting valuable teaching time.

For example, most people will only ever have one ssh key on their device. Having to setup the keyring, and keeping aware of its nuances, is a waste of time.

Post reply on HN