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

341–350 of 353 posts

Re: Git password authentication is shutting down

#341

Post by DangitBobby »

GuB-42 wrote: post #290
DangitBobby wrote: post #130

For those of you who are saying you don't really "know" git, your VCS will be so so much less stressful if you take a day or so to learn it! I can't recommend this site enough for familiarity with the basics: https://learngitbranching.js.org/

The news is not actually about git, it is about GitHub. Maybe they should make it more explicit in the title. Git still supports password authentication, as well as many other protocols. GitHub chose to restrict which protocols and authentication schemes are allowed on its platform. But obviously, learning about the tools you are using is always a good idea. My preferred "tutorial" is this one: https://codewords.recu…

I know, but a lot of discussion ended up being about git with people saying they didn't "get" it (heh), hence the link.

Re: Git password authentication is shutting down

#342

Post by u801e »

b3morales wrote: post #326
u801e wrote: post #209

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 question really should be why do we want to use git for version control when people really want an backup system where they can essential…

Frontend developers really like their designers to have versions, because it handles the eternal: Designer : Hey, I filed a bug for this, it doesn't look like the design. Developer : Um, we released that like two weeks ago; it's correct according to the design I had at the time. Designer : Yeah, but this is the design Maybe you can just fix it really quick today? Doesn't have to be git, but some way to match up relea…

A timestamp would be sufficient in that case. If you think of most editors and word processors, they have undo and redo features that allow users to go back and forth in terms of the history of their edits. Those features normally don't support branches and if you make a change in the middle of a redo, you lose access the rest of the other redo steps.

So you could tell the designer that you have the version they sent you on Friday August 13, 2021 at 3:12 PM EDT. Did they make any changes after that, or did they mean to send you a version they made prior to that?

Re: Git password authentication is shutting down

#343

Post by u801e »

happymellon wrote: post #221
u801e wrote: post #209

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 question really should be why do we want to use git for version control when people really want an backup system where they can essential…

Especially when they use tools that make files that contain all the history through "non-destructive changes" anyway. But I think the reason is because the mess of folders they then create in DropBox and they can never find their files. What would be great is if someone could make a TimeMachine for non-developers that uses git, because that is what they are doing in their heads anywy.

Most editors and word processors, along with other applications have undo and redo features that allow them to do that. If that could be tied with a timestamp, then it would be easy to see what version of the file they're working with. The only other feature they may find useful is a way to add a note to the file they saved indicating what changed (which would be the equivalent to a commit message).

Integrating those file(s) as a submodule or subtree in a git repository would work on the development side, but people who generate those files would have no need to interface with git, and people who use git would not need to use the editor for those files to get the history they need.

Re: Git password authentication is shutting down

#344

Post by 10000truths »

nemetroid wrote: post #270
10000truths wrote: post #251

Earlier quoted context omitted.

Uh... you can still do that today. python3 > print(“Hello world”)

>>> print(“Hello world”) File " ", line 1 print(“Hello world”) ^ SyntaxError: invalid character '“' (U+201C)

You can blame my iPhone for trying to "helpfully" convert my quotes into smart quotes. :(

Re: Git password authentication is shutting down

#345

Post by Cadwhisker »

voltagex_ wrote: post #160
Cadwhisker wrote: post #157

Earlier quoted context omitted.

It was a month ago and I didn't note down all my attempts. It went something like: Pushes were not working. I re-entered my password a few times, checked other config settings a few times before Googling the Git error message, which led me to find that GitHub's security policy was changing. I tried an SSH login (fail), switched to trying locally generated SSH keys. Used PuTTY's "puttygen.exe" to make an SSH key. Did…

I don't think I can recommend anyone use PuTTY on Windows anymore, partly because of issues like this. It might be that TortoiseGit is old, but ssh.exe should be available on Windows 10 now.

I still find PuTTY very useful, but domain spammers have managed to hijack the author's official page from the top of search-engine lists.

Re: Git password authentication is shutting down

#346

Post by AnIdiotOnTheNet »

zem wrote: post #338
AnIdiotOnTheNet wrote: post #309

Earlier quoted context omitted.

I think this way overestimates the value of both Git and source control in general for a lot of projects. Is this the result of the now common development methodology of using as many dependencies as possible or something?

no, it's often finding out the hard way that you have made a mess and it would be really nice to get back to the working state of an hour ago

It isn't that hard to just make a backup before you do anything messy. That's sorta what I'm getting at: people are using git as a really overcomplicated backup solution. It has the same problem: you forget to commit before making changes and you're still hosed.

Re: Git password authentication is shutting down

#347

Post by hnbad »

AnIdiotOnTheNet wrote: post #346
zem wrote: post #338

Earlier quoted context omitted.

no, it's often finding out the hard way that you have made a mess and it would be really nice to get back to the working state of an hour ago

It isn't that hard to just make a backup before you do anything messy. That's sorta what I'm getting at: people are using git as a really overcomplicated backup solution. It has the same problem: you forget to commit before making changes and you're still hosed.

Okay, but if you need to do "a backup" more than once, you will inevitably come up with your own shoddy versioning system, even if it consists of littering your project with files named "Copy of 2017-04-20_main_v1 (17).bak.new.old.bad.cpp~".

The alternative is just doing what you always do on every project: run "git init" and occasionally do a "git add -i && git commit". Even if you end up with a lot of non-descriptive snapshots name "WIP" at least you have something resembling a chronology and you can track changes across multiple files at the same time.

If your hobby projects mostly consist of single files with thousands of lines that are easy to unambiguously make copies of for backups, I won't judge you, but your experience is definitely not universal.

Re: Git password authentication is shutting down

#348

Post by bostonsre »

cxr wrote: post #330
bostonsre wrote: post #125

Earlier quoted context omitted.

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

That's not "pretty much like a wiki". That's the antithesis of a wiki. You've just described what the wiki was created to replace.

That seems a little drastic, how is it the opposite of a wiki?

What are the steps to edit a wiki? Click edit page, make changes, add comment and submit. That sounds like almost the exact same steps to me.

Re: Git password authentication is shutting down

#349

Post by [deleted] »

bostonsre wrote: post #348
cxr wrote: post #330

Earlier quoted context omitted.

That's not "pretty much like a wiki". That's the antithesis of a wiki. You've just described what the wiki was created to replace.

That seems a little drastic, how is it the opposite of a wiki? What are the steps to edit a wiki? Click edit page, make changes, add comment and submit. That sounds like almost the exact same steps to me.

[deleted]

Re: Git password authentication is shutting down

#350

Post by cxr »

bostonsre wrote: post #348
cxr wrote: post #330

Earlier quoted context omitted.

That's not "pretty much like a wiki". That's the antithesis of a wiki. You've just described what the wiki was created to replace.

That seems a little drastic, how is it the opposite of a wiki? What are the steps to edit a wiki? Click edit page, make changes, add comment and submit. That sounds like almost the exact same steps to me.

Try actually measuring it. Fix the 404 link:

https://github.com/solid/solid-rest

(It's the only link in the file.)

Make sure you don't have your thumb on the scale.

Post reply on HN