Git password authentication is shutting down • Hacker News Board

Re: Git password authentication is shutting down

#351

Post by AnIdiotOnTheNet » Thu, Aug 19, 2021, 2:13 PM UTC

hnbad wrote: post #347

AnIdiotOnTheNet wrote: post #346

Earlier quoted context omitted.

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-descripti…

> The alternative is just doing what you always do on every project: run "git init" and occasionally do a "git add -i && git commit".

Or I just let my backup software handle it. Automated daily backup supplemented with manually initiated backup if I need a specific point-in-time snapshot.

This isn't rocket science.

Re: Git password authentication is shutting down

#352

Post by cxr » Fri, Aug 20, 2021, 8:42 PM UTC

cxr wrote: post #350

bostonsre wrote: post #348

Earlier quoted context omitted.

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.

The unwillingness to venture into territory that would make the previous claims quantifiable (and falsifiable) is noteworthy.

    $ sha256sum "./PR?-ORLY.txt" 
    52028d35999a481e7cb19b14eae3bf66cb7c9c4fe2e15b56b55f3ccadffeee1f  ./PR?-ORLY.txt
    $ cat "./PR?-ORLY.txt" 
    Did you commit to source control and submit a pull request to post this comment?

Re: Git password authentication is shutting down

#353

Post by doubleunplussed » Sat, Aug 21, 2021, 3:02 AM UTC

ajtjp wrote: post #316

doubleunplussed wrote: post #163

What's the recommended way to manage git clones on shared computers now? In the past, multiple people would use these computers, and would push and pull using their own github credentials. I'm talking lab computers in a research context, where there is a shared login to the computer, but where we use our own github credentials to access a shared repo we all have commit rights to. Now what are we supposed to do? I don…

Not necessarily recommended , but something that was done by a real team at a real company. We all had our own GitHub Enterprise accounts. But only one was logged on to each computer. Rather than switch out the accounts when someone else used a computer, we just included the initials of whoever was making the commit in the message. E.g. DU: Fix some bug, if Double Unplussed was making the commit. This only really wor…

That's an orthogonal issue, we already use a pre-commit hook that prompts for the committers name instead of caching it. Who commits is one thing, who authenticates a push is another.

I guess we could have a shared github account and I could give it commit rights to the specific repositories. But that's still pretty silly that I should have to do that.