When did using git commands become so complicated?
Post number #794410, ID: 6b561e
|
A year and half ago you just needed to enter your credentials once to do some pulls and commits on your private repos, and now you first need to create a personal token, then some ssh keys, and associate them to your user, and more that I still expect to find...
Ffs, I just wanted to do a small commit on an old repo. Why is it so frustrating?
Post number #794803, ID: d83dc2
|
how is generating a key pair and copy pasting the pub key complicated? it takes seconds
Post number #794804, ID: d83dc2
|
it's way less effort then confirming an email, we should just use key pairs instead of accounts...
Post number #794806, ID: d83dc2
|
but i guess mandating it is kinda shitty
This. You can even set it passwordless (not that I would do it...), and then pull and push without needing to do anything else.
Post number #795062, ID: 2b9490
|
Git commands didn't change in years. As for github, no one is telling you to use it.
Post number #795321, ID: 6b561e
|
>>794803 it takes seconds if you know how to do it, which was not my case. Github itself gives a link to show how it's done, but the whole process is explained in 4 different links, and that was kinda frustrating.
Post number #795693, ID: fd849e
|
>>795321 Yeah Github's documentation for this is out of whack for some reason. The actual process is fairly simple. It's not Git's fault though, just Github's.
Total number of posts: 8,
last modified on:
Sat Jan 1 00:00:00 1634545667
| A year and half ago you just needed to enter your credentials once to do some pulls and commits on your private repos, and now you first need to create a personal token, then some ssh keys, and associate them to your user, and more that I still expect to find...
Ffs, I just wanted to do a small commit on an old repo. Why is it so frustrating?