so before that we had a password transmitted over internet. now we have the token transmitted over internet, which is just a longer password. a serious upgrade...
You always have to transmit something over the internet. Yes, making the changes is tedious, but I think Oauth does a good job, and my understanding is, git sticks to Oauth best practices. The difference to password is, that you can limit the access, also can temporaryily change access rights.
FINALLY. Great video. I wasted so much time because I didn't give my new token any permissions.... big dumb, got frustrated and I should have just slowed down... Thank you.
Thank you and God bless you brother, it's amazing how often we, well I, forget the simple things in computing. Your video reminded me that the password, though accepted, is not shown. I was expecting **** are something and thus it was working all along if I had just clicked the Enter key. Thanks again for reminding me of the basics.
I'm sure a lot of other people were pulling their hair out after github made this change. lol I couldn't tell if I was pasting the token into WSL, as the right-click doesn't give you the normal menu like on native Ubuntu. Nothing I tried seemed to work for that, so I had to MANUALLY type the token for the first git push. Then used the cache option, and it remembered the token the next time I opened WSL. Thanks for the vid. Super helpful. ;)
just FYI if you're on mac you may have to manually open your keychain and delete the GitHub entries. Various git config settings (system/local/global & even XCode) seem to be setup to check keychain first and will thus use your old password.
What these instructions don't tell you is that your Personal Access Token (PAT) will only be cached for around 10 minutes. After that you'll need to keep entering the PAT as your password again.
i followed all this and i keep getting: remote: Support for password authentication was removed on August 13, 2021. Please use a personal access token instead. Even though i already did it.
Same! I had my password already setup so there was no need to type in everytime. Now I need to put the token on the password field but git doesnt ask me for the password, just gives me the error.
@@actuallymarcos8606 I figured it out for my computers (running MacOS), i had to clear the git cache this way on terminal: "git credential-osxkeychain erase". Then clone a private repo and then enter my email and password (token). I was clearing the git credentials a different way and trying to push code which wasn't working.
The only thing I had to do different was use: "git config credential.helper wincred" -- for my WIN10 laptop. Otherwise I got a UNIX error. Everything else worked like a charm! Thank you!
Thanks for this tutorial, just it warns (Submitting this form will generate a new token. Be aware that any scripts or applications using this token will need to be updated. ) so my question is Every time I need to push my changes to the git if I regenerate the key is that will affect the code and upateds on the git. Or I need to keep this generated token in a text file or some where save to keep using the same key for all updates? As I understand from the video it is ok to regenerate the token and continue woking, so correct me please if I am wrong
Thanks a lot this was very helpful. One modification for Windows users. If you use git bash on Windows, you may encounter the following error after following these instructions. Error fatal: credential-cache unavailable; no Unix socket support This is because git bash does not use Unix sockets on Windows. Instead of setting credential.helper to cache, set it to wincred: git config --global credential.helper wincred
Thank you so much for this! Very helpful after a lot of frustration trying to read through the documents on my own.
Yes usually documentation on these topics sucks
so before that we had a password transmitted over internet. now we have the token transmitted over internet, which is just a longer password. a serious upgrade...
And There is nothing we could do🥲
You always have to transmit something over the internet. Yes, making the changes is tedious, but I think Oauth does a good job, and my understanding is, git sticks to Oauth best practices. The difference to password is, that you can limit the access, also can temporaryily change access rights.
@@narminaliyeva6175 nothing?
Solid tutorial. On point, no fluff. Thank you!
sheesh, 20 seconds in and I can tell its already gonna' be good
Oh!! Thanks a lot. Just moving last 2 hours here and there to figure it out ... Finally got it. I am setting up github to my remote VPS.
FINALLY. Great video. I wasted so much time because I didn't give my new token any permissions.... big dumb, got frustrated and I should have just slowed down... Thank you.
Thank you and God bless you brother, it's amazing how often we, well I, forget the simple things in computing. Your video reminded me that the password, though accepted, is not shown. I was expecting **** are something and thus it was working all along if I had just clicked the Enter key. Thanks again for reminding me of the basics.
I'm sure a lot of other people were pulling their hair out after github made this change. lol
I couldn't tell if I was pasting the token into WSL, as the right-click doesn't give you the normal menu like on native Ubuntu.
Nothing I tried seemed to work for that, so I had to MANUALLY type the token for the first git push.
Then used the cache option, and it remembered the token the next time I opened WSL.
Thanks for the vid. Super helpful. ;)
great stuff. But my existing environment never seems to re prompt me for the new credentials.
Same problem here.
same
same, it never ask me again for user password
Great walk through, thank you. Git should be paying you for this!
thanks
thanks
thanks
this ended a 13hrs mystry. Thank you so much
Thanks for this. I was pretty confused but the way you presented it makes it pretty simple.
Thanks, man for the solution you gave to re-entering/pasitng the token again & again.
Thank you sir its very very informative. after many days effort at last i found to the point video. thank you sir once again
Was trying to push a project and I got this issue. Thank you.
Thanks ! the cache command saved from copying and pasting the "Access token" each time ! :D
just FYI if you're on mac you may have to manually open your keychain and delete the GitHub entries. Various git config settings (system/local/global & even XCode) seem to be setup to check keychain first and will thus use your old password.
THANK YOU SO MUCH. I was struggling to do this. I didn't know where to write my token.
very well done! so swag, thanks! can't believe it was such a minor fix, liked the way you summarized the tokens simply
Thank you Ed. Just what I needed.
Great tutorial that helped deal with tokens frustrated issue. Great thanks!!
Thanks, Ed Goad, you're the best
Thank you so much... I spent sleepless night because of this password issue.. Was wondering why nothing was showing as I typed/pasted... Thanks a lot
Man you saved me I have been struggling this password token. Thanks alot
Thanks. I finally needed to work this out as we get closer to the decommissioning day
Thanks Ed. Exactly what I was looking for :)
This is very helpful. You save the day. Much Appreciated.
You saved me a lot time sir, thank you very much.
What these instructions don't tell you is that your Personal Access Token (PAT) will only be cached for around 10 minutes. After that you'll need to keep entering the PAT as your password again.
Who gona save my day toniiiiiight!? oh oh oouw))) Thank you so much!
Amazing tutorial, all we need it. Thanks man
Thank you for making this look easy
That was helpful, and it also works with Personal Access Tokens.
Short and clear ☺, thanks for the video Dude.
It's a FKIN PASSWORD OH MY GOD... thank you man.. I stuck with this as begginer, I copied this but didn't knew what to do with it xD
Thanks boss, who needs reading when u got videos like this lols
worked like a charm!
If git config --global credential.helper cache is not working for you, use the following command instead :
git config --global credential.helper store
Thank you so much! 🥲
My brain exploded like Nagasaki but i slowly understood the whole video the more i watched it
Thank you! just what i needed
i followed all this and i keep getting: remote: Support for password authentication was removed on August 13, 2021. Please use a personal access token instead. Even though i already did it.
Same! I had my password already setup so there was no need to type in everytime. Now I need to put the token on the password field but git doesnt ask me for the password, just gives me the error.
@@actuallymarcos8606 I figured it out for my computers (running MacOS), i had to clear the git cache this way on terminal: "git credential-osxkeychain erase". Then clone a private repo and then enter my email and password (token). I was clearing the git credentials a different way and trying to push code which wasn't working.
@@MarsTheProgrammer Thanks for replying bro! I will try your solution and see if works for me too.
I have a personal access token working, but it seems to only work for one of my git repositories. Do I need to make one for each new project?
Worked for me. Thanks for the demonstration!
You save my happy in job Thanks a bunch from
manikandan -- INDIA -Tamilnadu
Very pedagogical tutorial. Thank you.
Thank you so much, it helped me access my github repo
@7:05 Command for saving the token so that you dont have to type it every time
Thank you man!! I trying to do this s*** for a week
Very straight forward. Thank you sir!
This is the best video ever
Thanku so much. Really Solved a big problem for me.
You are present perfect of programming!
Thank u. you save my life 3 times.
☺That's so so much helpful.... I m thankful for this best tutorial 😘
Mine is not working.. it says fatal, not a git repository.. please help
Thanks for your video, it helps me a lot
Good video, easy to follow instructions.Thanks!
STRAIGHT TO THE POINT. Amazing. Thank you!
Thank you, very clear!
You are a genius!. Like and subbed!
great video - thank you very much for putting this together so well
Thanks man . I learned a valuable thing 💫
gracias, no entendía como era pero ahora si quedo funcionando
Thank you so much! Extremely helpful.
Thanks for creating this helpful video 😄😄
What did you paste at 5:33?
Excellent tutorial, I really appreciate it, man
Thank you so much. I get frustrated cos each time I have to copy some random strings somewhere (PAT)
Thank you Ed! I appreciate the help!
Made my day! Thanks a lot mate.
But even after using token it is not asking me for entering thi after every command
same
not asking should be a good thing , lol
This video helped a lot , thanks boss
Many thanks my friend!
Excellent tutorial. Thanks so much Ed!!
Hi, what happens if a user leaves the organization that creates PAT. How to assign PAT to a new user or service account.
How about using the token on a repo where you are a contributor, not an owner?
Thank you. Excelent tutorial.
The only thing I had to do different was use: "git config credential.helper wincred" -- for my WIN10 laptop. Otherwise I got a UNIX error. Everything else worked like a charm! Thank you!
Really helpful, thank's a lot!
excellent video! provided all the required info. thanks
THANKS DUDE!!! very usefull tutorial
Thanks for this tutorial, just it warns (Submitting this form will generate a new token. Be aware that any scripts or applications using this token will need to be updated. ) so my question is Every time I need to push my changes to the git if I regenerate the key is that will affect the code and upateds on the git. Or I need to keep this generated token in a text file or some where save to keep using the same key for all updates? As I understand from the video it is ok to regenerate the token and continue woking, so correct me please if I am wrong
Okay I have tried cache but after closing and reopening the terminal I'm still asked to provide user name and password 🔑
Very simple and helpful, Thanks a lot
Awesome video, thank you so much
Thanks Man. You saved me
Very good explanation
It helped me on my Linux Manjaro. But I don't understand why adding the token earlier directly to VS code didn't help 🤔
Thanks a lot this was very helpful. One modification for Windows users.
If you use git bash on Windows, you may encounter the following error after following these instructions.
Error fatal: credential-cache unavailable; no Unix socket support
This is because git bash does not use Unix sockets on Windows. Instead of setting credential.helper to cache, set it to wincred:
git config --global credential.helper wincred
Very accurate information. Thank you!
Thankyou so much, nice tutorial, you help me to solve the problem very easy :), do more videos
Very clear tutorial. It helped me a lot ❤
is there a way to see your token number again after creating it , lets say you forgot to store it that time
It says repository is not found I literally tried everything and I can’t do it someone help please
Thanks dude - you helped me a lot. Exactly what I was looking for :-) Especially the credential caching is very useful :-)))))
Super cool, it helped!
That helped a lot, thank you!
Thank you chief!
Useful! Thank you.
thank you soooo much, i now understand it.
Solved my problem. Thanks.