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

131–140 of 353 posts

Re: Git password authentication is shutting down

#131

Post by francislavoie »

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

Re: Git password authentication is shutting down

#132

Post by javajosh »

Hot tip for IntelliJ users: add your github account to the IDE (in project settings) and the IDE will use an OAuth token for git access on that account.

(I think the way it's structured is that Jetbrains is the OAuth provider, and Github is the relying party, which implies that you need to make sure your Jetbrains account is secure. It also means that if you want the best security you'll stick with the tried-and-true private-key-in-.ssh-public-key-on-remote solution)

Re: Git password authentication is shutting down

#134

Post by francislavoie »

DangitBobby wrote: post #128
chaorace wrote: post #124

Earlier quoted context omitted.

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 :)

Yeah. "git pull" is so bad. I wish it didn't exist. Every single time a coworker has gotten into a stuck state is because they used "git pull" which made a merge commit when there shouldn't have been one. It's mostly stopped happening since I yelled at everyone to _please_ configure their machine with ff-only.

Re: Git password authentication is shutting down

#135

Post by jackcviers3 »

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 weep for the world now that git is too difficult to understand.

It used to explain itself through building your own version of git. You have a file named hash that tracks changes on each file named foo... now all the changes are in a directory named hash...now your changes have to be merged with others...

It's kind of up there with next steps after if then else fi. Some things will always be difficult, but diffs and commit and picking one of two possible diffs from two windows should not be one of them.

Re: Git password authentication is shutting down

#136

Post by francislavoie »

northwest65 wrote: post #118
cstrat wrote: post #100

Earlier quoted context omitted.

wait there is another way?

I've used GitExtensions from the start of my Git usage. I've never had to blow any of my repos away at any point. I also use things like Rebase without thinking about it, something which from what I've read on here is considered a slightly unusual/difficult task. Using GitExtensions means I can use Git as easily as any other tool, I never give it a second thought. I see the command line commands being executed, but n…

I used GitExtension for years, but then I switched to Linux some years ago, so I had to find an alternative. I used SourceTree for a while, but I hated the UX. I tried GitKraken when it first came out, but it had a lot of issues that didn't make it appropriate for my workflow. After a couple more years, GitKraken had improved enough that I was able to switch to it. I've been using it for maybe 4 or 5 years now.

Re: Git password authentication is shutting down

#137

Post by jcrites »

DangitBobby wrote: post #128
chaorace wrote: post #124

Earlier quoted context omitted.

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 :)

The command you want is "git pull --rebase". There are configuration settings to make "git pull" rebase by default, and I'd recommend always turning that on that default (which may be by why the person above omitted it from his pull command).

I actually thought "git pull" did "git pull --rebase" by default (this may be what you get from running `git --configure` without modifications?), but maybe I've just been configuring it that way. You can achieve this in your global Git configuration by setting "pull.rebase" to "true".

I don't think it's sane behavior for "git pull" to do anything else besides rebase the local change onto the upstream branch, so I'm surprised it's not the command's default behavior. Has the project not changed the CLI for compatibility reasons or something?

When do you ever want a "git pull" that's not a rebase? That generates a merge commit saying "Merge master into origin/master" (or something similar) which is stupid. If you really want to use actual branches for some reason, that's fine, but "merge master into master" commits are an anti-pattern that if I ever see in a Git repository I'm working on or responsible for, results in me having a conversation with the author about how to use Git correctly.

Re: Git password authentication is shutting down

#138

Post by francislavoie »

qwerty456127 wrote: post #133

Very sad. An unfriendly move needlessly forcing unnecessary complexity. People should be able to decide this for themselves.

That's not how security works. Give users the easy option, and they'll take it. For things to be secure by default, you need to disallow or _heavily_ discourage all potentially insecure options.

Re: Git password authentication is shutting down

#139

Post by Cadwhisker »

I use TortoiseGit under Windows. It took me 3 days (on and off) to figure out how to push code to my repositories again. The amount of misleadng and confusing information on the internet is extraordinary.

Signed: a developer with well over a decade of experience in version control, *nix, Windows, crypto, etc.

Post reply on HN