If you're having a hard time saving the file in vim like I showed, here's a quick explanation: - If you're following along, after I type in the file I press `ESC` (the escape key) on my keyboard to enter "command" mode - Then I type `:wq` to write/save and quit out of vim. - If you get stuck, my suggestion is hit `ESC` a few times before typing `:wq` You can also edit the file however you typically edit files like in a GUI text editor like VS Code. Or use a different command line editor that is more beginner friendly by replacing "vim …" in the command line with something like "nano …". > In retrospect, I shouldn't have used vim to edit the file for a tutorial like this since I'm sure plenty of viewers aren't familiar with vim which is reflected in the most common comments so far. I'll keep that in mind for future videos. Plus, maybe this is a good excuse on making a simple "Basics of vim" video ; )
lol glad it helped! But yeah, I probably should have used a different editor instead of vim for this tutorial 😅 There definitely seems to be enough people unironically "trapped" in vim that I'll have to think about using it again for future videos!
@@VictorsOtherVector after I find out what vim is, I think it’s kinda cool tbh. But just please tell people to hit the esc button. I didn’t see your explanation in the comment section until after I googled vim and calmed down 😂😅
That's amazing; thank you for the compliment! Now we just need this video to be the first on the search! (Google: "Did you mean... this amazing tutorial on SSH keys for GitHub?" 😉)
This video was such a lifesaver! Struggled to set up an SSH key for a while. After watching many videos I wondered why it was not working. But you showed me, when you are asked to enter yes/no/finngerprint for testing, you answered yes... I kept giving the fingerprint forever (the actual GitHub documentation was very confusing) and it didn't work. Now I can clone a repository with SSH key. Thank you so much!
That is wonderful to hear you came back to this! Crazy to think this video has been up long enough that you could come back to it for reference a whole year later! (You're definitely not the only one who did exactly this 😆)
We all gotta start somewhere, i can only wonder what the beginners like me are doing now after a year or two watching this tutorial! Thanks alot for the help!
Really does make you wonder, especially after seeing this video has almost 150k views... Based on some of the comments, it looks like a decent amount come back a year to watch the video again 😆 Honestly it doesn't surprise me and it's a good thing to know where to go to fix something. The 2nd time doing something is usually a lot faster. My suggestion: Come back every year to rewatch this video. Heck, why not every week?! ; )
huge appreciation for including the section on changing the remote. This is what I needed and what makes the ssh key actually usable, and is not included in the official tutorial.
Good to hear you found that part useful! I debated including that originally since it wasn't the main topic, but decided to keep it since I knew it was a common nuance that a lot of people miss when originally learning the basics of git. I'm glad it helped at least one person! :D **Quick edit for anyone looking for when I mentioned about this specifically. It's at about **9:45** in the video.**
Thank you so much, I tried setting up the SSH key just by reading the documentation but when I tried the college firewall won't let me, lol. When I got back to my house I didn't want to re-read the whole thing so you saved me a lot of time!
This video, was EXACTLY what I needed. Been coding from the same computer for so long that I completely forgot how to generate SSH Keys, and add them to the SSH Agent. Huge THANK YOU. Definitely subscribing, and liking. 👍
Yay! I'm so happy to hear it was helpful! The big motivation of making this video was knowing that basically no one remembers how to get SSH keys working for GitHub! I have yet to meet anyone who actually can do it without looking it up 😆 Again, so great to hear it was helpful! And thanks for watching & subscribing! Hoping to more videos on software engineering, data science, and machine learning! (I have some ideas cooking up in the oven)
Thanks! That means a lot! I really wanted to make sure that I had this video be useful over anything else. The plan is to put more videos soon that focus on actually being useful (especially for data science & machine learning) so hopefully you'll find future videos still worth subscribing 😄
@@VictorsOtherVector No doubts about it. Il will be interesting. Actually i'm in a "bash scripting, vim, linux" period, and will check python next, so it sounds nice.
Thank you very much! I followed along with the GitHub document in Windows and it worked perfectly! Appreciate your detailed descriptions and explanations.
Thank you! It means a lot that you liked it and it was a cohesive tutorial! My goal was to make something that could easily be referenced without it being too long of a video.
Thanks a lot man. I don't know what i screwed up in my terminal on windows when trying to delete and install ohmyzsh and when I changed my username. I have been maniacally trying to repair this error since 2 days where I was unable to clone anything. You finally fixed the error. Thanks a lot
Thank you so much this is a very good tutorial. For future tutorials or anything you do make sure to keep the typing part in the middle of the screen or simply clean console before type new commands so the typing can always be on the top otherwise it is quite hard to read with the RUclips seekbar. This is just a suggestion good job.
Thank you for the kind words and suggestion! Definitely something I'm going to look at doing for future videos. I considered it but I thought it could be a bit too confusing for beginners if I were to clear the terminal. But I hadn't considered that RUclips might block part of the screen while people follow along. Thanks again for the suggestion!
Hey Victor, This videos seems to be the first and complete guide how to set up SSH Keys for GitHub. Other sources tend to dive way too deep imho. Thank you very much!
Thank you so much for this man I was looking to deploy a project I made and I was looking at the old ways of doing it via github and it told me that this is the way to do it now. Your explanation was so clear and concise.
You're welcome! It's so great to hear that it was so helpful to you! I can totally understand how a "text tutorial" isn't always enough; sometimes you just need to see it done in (near) real time!
Good question- In retrospect, I shouldn't have used vim to edit the file for a tutorial like this. If you're following along, after I type in the file I press `ESCAPE` on my keyboard to enter "command" mode and then type `:wq` to write/save and quit out of vim. If you get stuck, my suggestion is hit `ESCAPE` a few times before typing `:wq` You can also edit the file however you typically edit files. Or use an editor that is more beginner friendly by replacing "vim …" in the command line with something like "nano …" I hope that helps!
So happy to hear it was helpful! It can be a bit intimidating when you're first learning about it. I was hoping to put something that more easily showed the process visually, so it's awesome to hear you and others found this helpful!
Great question; I think responded to this in a different comment to a question that's deleted now. But in short, since I'm using vim you'll have to hit the `ESCAPE` key to enter into "command mode" and then type `:wq` (you should see it at the bottom of the terminal. If it doesn't work the first time, I suggest hitting `ESCAPE` a few extra times and trying again 😄 In retrospect, I probably should've used an editor that's easier to navigate for people who haven't used vim before. I'll probably make a pinned comment since you're not the first to ask this exact thing 😅
DAMN BRO I REALLY THANK YOU SO MUCH, I'm wondering why my rsa key won't work for 2 years I've been stuck with that. But now I THANK YOU SO MUCH GOD BLESS YOU, you solved my problem!
Thank you! That means a lot! 😄 I really tried to make it digestible & as straight to the point. (Trust me when I say I've had whole live lessons/lectures that went beyond 30mins on this exact thing)
Good question- In retrospect, I shouldn't have used vim to edit the file for a tutorial like this. If you're following along, after I type in the file I press `ESCAPE` on my keyboard to enter "command" mode and then type `:wq` to write/save and quit out of vim. If you get stuck, my suggestion is hit `ESCAPE` a few times before typing `:wq` You can also edit the file however you typically edit files. Or use a different command line editor that is more beginner friendly by replacing "vim …" in the command line with something like "nano …" or even a GUI text editor. I hope that helps!
Good question- In retrospect, I shouldn't have used vim to edit the file for a tutorial like this. If you're following along, after I type in the file I press `ESCAPE` on my keyboard to enter "command" mode and then type `:wq` to write/save and quit out of vim. If you get stuck, my suggestion is hit `ESCAPE` a few times before typing `:wq` You can also edit the file however you typically edit files. Or use a different command line editor that is more beginner friendly by replacing "vim …" in the command line with something like "nano …" or even a GUI text editor. I hope that helps!
Since I'm using vim here, I went into "command mode" by hitting the escape key and then typing ":wq", and then hitting the enter key. But if you edit this file with another editor, you'll do whatever it is to save from there And by the way, this was a good question; vim is notorious to beginners for the seemingly obscure way you save and exit!
@@fahimaqalanjo8590 If you're in the vim editor and you can't save, it's possible you're not in command mode. You can make sure by hitting escape multiple times before entering :wq If that still fails, hit escape (a few times) and try SHIFT+Z SHIFT+Z In retrospect, I probably shouldn't have shown editing the file in vim since some people won't be familiar. But you can do the same thing with another editor as long as you keep the file name and the contents the same Hopefully all that is helpful!
Hello, When I try to test the connection using ssh -t .... , it is showing ECDSA key fingerprint and asking whether to continue or not. Here, the key fingerprint is not matching with the listed one. Could you please help me on this?
Hmm, it sounds like the key you set up wasn't verified. I think you should just have to approve it on GitHub. At worst, you should simply be able to do the same process from the video to create a new key Here's a link to the official documentation that I think addresses your exact situation: docs.github.com/en/authentication/troubleshooting-ssh/error-were-doing-an-ssh-key-audit Could be wrong though without knowing the full output. But I hope that helps & fixes your issue!
Nice! Thanks for sharing! I don't typically use Windows so my advice has been to suggest the "Git Bash" tool. But I've heard good things about wsl so good to know this is an option!
So I assume you're talking about your email address which we provided to generate the SSH key. In short, you need to provide the email that GitHub already knows about. This is what GitHub uses to keep track of who made a commit. But you should know that whatever email you put in there will be public. Thankfully GitHub has a solution; they provide a private email that's associated with your account that you can use. You can then use that private email address for your SSH key. Here's the official docs on that: docs.github.com/en/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-your-commit-email-address Hope that's all helpful!
Followed step by step, no matter how many different ways and times I try adding the ssh agent (what you did around 6:10), it either says "No such file or directory" or "invalid format". Any help appreciated!
Hmm, you might want to make sure you have the file created and has the file contents I show exactly written. It'd be my guess that it's the file and not the command (`ssh-add ...`) Make sure the name and path of the generated file from the `ssh-keygen` step. And then make sure the config file (in the video it was `~/.ssh/config`) references the correct generated file. It might be helpful to also read through the official GitHub documentation on this: docs.github.com/en/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent I hope that helps & good luck!!
Great question- I explained this in the pinned comment, but in short I'm using vim which requires you to hit `ESC` (on the keyboard) and then type `:wq` before hitting `ENTER` In retrospect, I should've used a more beginner friendly command line editor but I'm so used to using vim I didn't think much of it when recording the video. Oops 😄
thanks for helping with my doubts on this one, however i cant seem to push my folder to my git repo. the add and the commit has been done, it just isnt pushing, showing me an authentication error
Thanks! I might but you should know you can simply just do the same process on your computer but just go through the steps with a different GitHub account. If you do it right, your computer should handle it pretty seamlessly 😄
Oh I couldn't tell you exactly what I had that I had here (I change my config frequently), but I will tell you it was zsh (not bash) You might want to check out powerlevel10k for some of the theming I use. Also, this repo for autosuggestions that I found super useful: github.com/zsh-users/zsh-autosuggestions
incase you get stuck at eval. install wsl and type "bash" in the at the point u had the eval problem. or better still type bash if u already have wsl installed
Thanks for the tip! I'm definitely a unix-guy myself and I'm less familiar with using Windows. I've also have had luck installing and using Git Bash on Windows
If you're having a hard time saving the file in vim like I showed, here's a quick explanation:
- If you're following along, after I type in the file I press `ESC` (the escape key) on my keyboard to enter "command" mode
- Then I type `:wq` to write/save and quit out of vim.
- If you get stuck, my suggestion is hit `ESC` a few times before typing `:wq`
You can also edit the file however you typically edit files like in a GUI text editor like VS Code. Or use a different command line editor that is more beginner friendly by replacing "vim …" in the command line with something like "nano …".
> In retrospect, I shouldn't have used vim to edit the file for a tutorial like this since I'm sure plenty of viewers aren't familiar with vim which is reflected in the most common comments so far. I'll keep that in mind for future videos. Plus, maybe this is a good excuse on making a simple "Basics of vim" video ; )
I literally freaked out for a good 3 minutes when you get to the :wq part lol Thanks for putting the instruction up here
lol glad it helped! But yeah, I probably should have used a different editor instead of vim for this tutorial 😅 There definitely seems to be enough people unironically "trapped" in vim that I'll have to think about using it again for future videos!
@@VictorsOtherVector after I find out what vim is, I think it’s kinda cool tbh. But just please tell people to hit the esc button. I didn’t see your explanation in the comment section until after I googled vim and calmed down 😂😅
Thankyou, you just saved me. xD
Or you can use nano instead vim, it's simpler
30 minutes googling around with no information as clear as this tutorial. Works perfectly. Thanks a lot!
That's amazing; thank you for the compliment!
Now we just need this video to be the first on the search!
(Google: "Did you mean... this amazing tutorial on SSH keys for GitHub?" 😉)
This video was such a lifesaver! Struggled to set up an SSH key for a while. After watching many videos I wondered why it was not working. But you showed me, when you are asked to enter yes/no/finngerprint for testing, you answered yes... I kept giving the fingerprint forever (the actual GitHub documentation was very confusing) and it didn't work. Now I can clone a repository with SSH key. Thank you so much!
Yay! I'm so glad you got it figured out! And it's an extra bonus to know it was my video that specifically was able to help you!
I did this a year ago with my old PC and now here I am again. It still works . This tutorial is perfect, thank you once again.
That is wonderful to hear you came back to this! Crazy to think this video has been up long enough that you could come back to it for reference a whole year later!
(You're definitely not the only one who did exactly this 😆)
Two years later, and this video is stil the best! Well done!
We all gotta start somewhere, i can only wonder what the beginners like me are doing now after a year or two watching this tutorial! Thanks alot for the help!
Really does make you wonder, especially after seeing this video has almost 150k views...
Based on some of the comments, it looks like a decent amount come back a year to watch the video again 😆
Honestly it doesn't surprise me and it's a good thing to know where to go to fix something. The 2nd time doing something is usually a lot faster.
My suggestion: Come back every year to rewatch this video. Heck, why not every week?! ; )
huge appreciation for including the section on changing the remote. This is what I needed and what makes the ssh key actually usable, and is not included in the official tutorial.
Good to hear you found that part useful! I debated including that originally since it wasn't the main topic, but decided to keep it since I knew it was a common nuance that a lot of people miss when originally learning the basics of git. I'm glad it helped at least one person! :D
**Quick edit for anyone looking for when I mentioned about this specifically. It's at about **9:45** in the video.**
i love how direct to the point this tutorial is and the explanation is on point! thank you for making this video!
Thanks! Definitely what I was trying to go for so it means a lot you felt that way!
Very useful, I've not used githib in a year and needed a quick walkthrough to set this up!
thank you
It's good to hear that it was helpful after your year hiatus! 😄
Thank you kind Sir. Had to reset my machina, couldn't clone my repos...than the algorithm gods blessed me with your video. Life saver..
Good to hear the algo-gods brought you with my video that could help!
SSH keys with SAML SSO
Thank you so much, I tried setting up the SSH key just by reading the documentation but when I tried the college firewall won't let me, lol. When I got back to my house I didn't want to re-read the whole thing so you saved me a lot of time!
This video, was EXACTLY what I needed. Been coding from the same computer for so long that I completely forgot how to generate SSH Keys, and add them to the SSH Agent. Huge THANK YOU. Definitely subscribing, and liking. 👍
Yay! I'm so happy to hear it was helpful!
The big motivation of making this video was knowing that basically no one remembers how to get SSH keys working for GitHub! I have yet to meet anyone who actually can do it without looking it up 😆
Again, so great to hear it was helpful! And thanks for watching & subscribing! Hoping to more videos on software engineering, data science, and machine learning! (I have some ideas cooking up in the oven)
I subscribed to your channel just for that pure-gold video. Clear, nicely paced and without "youtube fluff" around. Thank you again.
Thanks! That means a lot!
I really wanted to make sure that I had this video be useful over anything else. The plan is to put more videos soon that focus on actually being useful (especially for data science & machine learning) so hopefully you'll find future videos still worth subscribing 😄
@@VictorsOtherVector No doubts about it. Il will be interesting. Actually i'm in a "bash scripting, vim, linux" period, and will check python next, so it sounds nice.
This was amazing Victor, really clear instructions for no native English speakers.
Thank you very much
You're welcome! I hoped it was clear and hearing that it was even for a non-native English speaker is a huge compliment!!
Thank you very much! I followed along with the GitHub document in Windows and it worked perfectly! Appreciate your detailed descriptions and explanations.
Great that you didn't have any issues being on Windows!
@@VictorsOtherVector Would have any upcoming tutorials on Heroku?
Thank you so so much. I spent the whole weekend trying to create an ssh key. This is the perfect video for beginners like myself. Thank you
So happy that you found the video so helpful!
I rarely comment on YT videos but this was an absolute life saver. Thank you!!
This is an amazing tutorial. I was finding bits and pieces online but no complete story like this. Thank you!
Thank you! It means a lot that you liked it and it was a cohesive tutorial! My goal was to make something that could easily be referenced without it being too long of a video.
Thanks Victor! Was on another tutorial about setting up git and they completely skipped this step so I was lost. So grateful for this video.
Oof, that can be super frustrating! But I'm happy that I was able to help!
Bro, live for 100 more years! Thanks!
Thanks a lot man. I don't know what i screwed up in my terminal on windows when trying to delete and install ohmyzsh and when I changed my username. I have been maniacally trying to repair this error since 2 days where I was unable to clone anything. You finally fixed the error. Thanks a lot
i had a difficult creating ssh keys but after watching this it helped me so much
Yay! Happy it helped you out!
Thank you so much this is a very good tutorial. For future tutorials or anything you do make sure to keep the typing part in the middle of the screen or simply clean console before type new commands so the typing can always be on the top otherwise it is quite hard to read with the RUclips seekbar. This is just a suggestion good job.
Thank you for the kind words and suggestion!
Definitely something I'm going to look at doing for future videos. I considered it but I thought it could be a bit too confusing for beginners if I were to clear the terminal. But I hadn't considered that RUclips might block part of the screen while people follow along.
Thanks again for the suggestion!
Dude you helped me so much where other tutorials fall short. Now I can read/write in mu github repo
Dude, thanks you so much. I had a hard time understanding this in Github docs.
You're welcome! It's great to hear the video was helpful even after reading the official docs!
this video is a life savior
🛟 Happy to have helped!
Very good explanation. I like how you break all the information into easy to understand parts.
Thank you- I tried my best to make the sections understandable & flow together well so I'm happy to hear you say that!
Hey Victor,
This videos seems to be the first and complete guide how to set up SSH Keys for GitHub. Other sources tend to dive way too deep imho. Thank you very much!
You're welcome! I'm so happy to hear you found this so helpful!
Thanks a ton dude, this was just perfect. Exactly what I needed. Clear and concise.
Thanks! Definitely what I was going on for so it's so good to hear you felt it was succinct!
I have never used Github before. This was so useful! Thank you!
You're welcome! Great to hear that as a newbie to GitHub you found it so useful! !
Thank you so much for this man I was looking to deploy a project I made and I was looking at the old ways of doing it via github and it told me that this is the way to do it now. Your explanation was so clear and concise.
So happy that I could help!
Thank you so much, Victor! Your video helps me figure out the issues which I cannot solve using the online tutorials in text.
You're welcome! It's so great to hear that it was so helpful to you!
I can totally understand how a "text tutorial" isn't always enough; sometimes you just need to see it done in (near) real time!
Thanks bro this video sorted out my issue. Appreciate your help and keep going :)
Great to hear it all worked out!
And thanks! I hope to keep making more tutorials 😄
Great tutorial! Super easy to follow and straight to the point.
Thanks! I tried to keep it a tight tutorial! (We don't need another 40+ min walkthrough 😅)
Thanks, best tutorial just in 10 mins. Love it !!
This video was excellent! Good pace, great job walking me through the process and explaining. Pro move showing how to verify things are working.
Thank you! I really tried to make it accessible & useful for others so it's really awesome to hear you say all of that about the video!
Extremely helpful, thank you and keep up the good work!
Thank you and it's great to hear it was so helpful!!
Thank you, this tutorial really helped me. You explained this really well. Sending you love and blessings from India.
Great Work. Keep posting like these tuts
Thanks! I hope to make something sometime soon but no promises ; )
@5:46: how did you save the file? i couldn't type wq over the INSERT
Good question- In retrospect, I shouldn't have used vim to edit the file for a tutorial like this. If you're following along, after I type in the file I press `ESCAPE` on my keyboard to enter "command" mode and then type `:wq` to write/save and quit out of vim. If you get stuck, my suggestion is hit `ESCAPE` a few times before typing `:wq`
You can also edit the file however you typically edit files. Or use an editor that is more beginner friendly by replacing "vim …" in the command line with something like "nano …"
I hope that helps!
@@VictorsOtherVector Thank you - I will try that :) - Thanks for getting back to me Victor, it means a lot ~
Nice clear, step-by-step explanation. Brilliant!
Thank you! :D
I watched many videos but this actually helped me, thanks
I'm so happy to hear it helped!
Thanks a lot for the tutorial! It worked. with the git bash.
I have been wondering on github docs for 30 min and i was about to give up!
So happy to hear it was helpful! It can be a bit intimidating when you're first learning about it. I was hoping to put something that more easily showed the process visually, so it's awesome to hear you and others found this helpful!
WHOA! Absolutely amazing tutorial. Thank YOU!!
Thank you! Makes me so happy that you liked it!
5:54 How did you save the file?? I cant put the last line (:wq)
Great question; I think responded to this in a different comment to a question that's deleted now. But in short, since I'm using vim you'll have to hit the `ESCAPE` key to enter into "command mode" and then type `:wq` (you should see it at the bottom of the terminal. If it doesn't work the first time, I suggest hitting `ESCAPE` a few extra times and trying again 😄
In retrospect, I probably should've used an editor that's easier to navigate for people who haven't used vim before. I'll probably make a pinned comment since you're not the first to ask this exact thing 😅
DAMN BRO I REALLY THANK YOU SO MUCH, I'm wondering why my rsa key won't work for 2 years I've been stuck with that. But now I THANK YOU SO MUCH GOD BLESS YOU, you solved my problem!
Wow, dude! Kept it straightforward and easy to understand! You're amazing!
Thank you! That means a lot! 😄
I really tried to make it digestible & as straight to the point. (Trust me when I say I've had whole live lessons/lectures that went beyond 30mins on this exact thing)
great tutorial, so easy to follow which sorted out my Permission denied (publickey) issues i was having 😃
Thank you! And so happy to hear the video helped you figure out your issues!
I'm following the video you have here. But, at 5:41 how did you save what you did and continue on?
Good question- In retrospect, I shouldn't have used vim to edit the file for a tutorial like this. If you're following along, after I type in the file I press `ESCAPE` on my keyboard to enter "command" mode and then type `:wq` to write/save and quit out of vim. If you get stuck, my suggestion is hit `ESCAPE` a few times before typing `:wq`
You can also edit the file however you typically edit files. Or use a different command line editor that is more beginner friendly by replacing "vim …" in the command line with something like "nano …" or even a GUI text editor.
I hope that helps!
Thanks a lot dude!❤ This tutorial was clear and easy
Best video ever. Nice and thorough. Thank you!
Aw, thank you so much! I of course can only focus on all the ways I'd want to improve it but I'll take that compliment :D
You really brought me time!! The whole last weekend I was trying!
So great to know I was able to help & you were able to figure it out!
thank you so much! ssh seemed daunting but this guide made it easy :)
You're welcome! Definitely can be intimidating the first (few) times so it's great to hear it was so helpful for you!
Wow! I'm speechless. Thank you very much for this tutorial. Excellent explanation and an amazing tutorial over all! Thank you
You're very welcome! It's so great to hear that you felt that I did a good job explaining! 😄
This Great man! I was having trouble trying to do any of this!!!
So great to hear I was able to help you out with it! It can be pretty intimidating/confusing when learning it the first time!
Thank you so much, man! This video is gold.
Wonderful and clear turorial. Thanks!
Thank you! It's great to hear you liked the tutorial!
Tks so much. There is so many time that i try. Finally works with your help. Thank you so much
You're welcome! It's so nice to hear this helped you!
this is so clearly explained , i am subscribing
The best video so far. Thankyou.
Precise, on point explanation! Thanks for making this video!
You're welcome! And so happy to hear you liked it! Really tried to make to make it concise (it easily could've been 3x as long)!
Thanks so much you have made it so simple to understand and to fallow
You're welcome! And I'm glad that you found it easy to understand & follow!
Thank you very much , very clear and concise, though I had to find my wayout in some steps. Much appreciated !
Thank you! And good to hear you were still able to get through the parts that might've been a little tricky for you!
Thank you so much! I was missing the fact that there is a separate SSH URL!
It's definitely a tricky one if you're used to using the HTTPS url for repositories!
Such an amazing Video. Thank You MAN.
Thank you! I'm happy that you liked it! :D
Thanks you so much for this, this is perfect. simple , concise and right to the point
You're very welcome! And I tried my best to do all those things so it means a lot that you felt it was simple but also concise!
Thank you so much for your clear explanation!
You're welcome! So happy to hear you found it clear!!
how do u save the file at 5:50
Good question- In retrospect, I shouldn't have used vim to edit the file for a tutorial like this. If you're following along, after I type in the file I press `ESCAPE` on my keyboard to enter "command" mode and then type `:wq` to write/save and quit out of vim. If you get stuck, my suggestion is hit `ESCAPE` a few times before typing `:wq`
You can also edit the file however you typically edit files. Or use a different command line editor that is more beginner friendly by replacing "vim …" in the command line with something like "nano …" or even a GUI text editor.
I hope that helps!
Thank you very eassy and clear explained🤗
You're welcome! And thank you! I tried to make it as clear and concise as I could!
Thank you _so_ much :D I had a lot of trouble, and this helped me all the way.
Yay! I'm so glad this was the thing that finally helped you get through it!
This is the best tutorial ever, thank!
literally thank you so much finally my setup done thank buddy
You're very welcome! So great to hear this helped with getting it all setup!
5:52 how did you save it
Since I'm using vim here, I went into "command mode" by hitting the escape key and then typing ":wq", and then hitting the enter key. But if you edit this file with another editor, you'll do whatever it is to save from there
And by the way, this was a good question; vim is notorious to beginners for the seemingly obscure way you save and exit!
@@VictorsOtherVector I did that and is not responding
@@fahimaqalanjo8590 If you're in the vim editor and you can't save, it's possible you're not in command mode. You can make sure by hitting escape multiple times before entering :wq If that still fails, hit escape (a few times) and try SHIFT+Z SHIFT+Z
In retrospect, I probably shouldn't have shown editing the file in vim since some people won't be familiar. But you can do the same thing with another editor as long as you keep the file name and the contents the same
Hopefully all that is helpful!
Simple tutorial loved it !
Thanks! I'm happy you enjoyed it so much!
Huge thanks man, did it on Linux and it worked just fine
You're welcome!
Also, Linux for the win!
Just what I needed!
hey There, this amazing video helped me a lot, thank you so much and have a nice day.
You're welcome and so happy it helped you!
(late to the response, but I did have a nice day 😄)
Hello,
When I try to test the connection using ssh -t .... , it is showing ECDSA key fingerprint and asking whether to continue or not. Here, the key fingerprint is not matching with the listed one.
Could you please help me on this?
Hmm, it sounds like the key you set up wasn't verified. I think you should just have to approve it on GitHub. At worst, you should simply be able to do the same process from the video to create a new key
Here's a link to the official documentation that I think addresses your exact situation: docs.github.com/en/authentication/troubleshooting-ssh/error-were-doing-an-ssh-key-audit
Could be wrong though without knowing the full output. But I hope that helps & fixes your issue!
If you are on a windows just install wsl "wsl --install" on power-shell. Write wsl and you can from there follow the instructions in the video.
Nice! Thanks for sharing!
I don't typically use Windows so my advice has been to suggest the "Git Bash" tool. But I've heard good things about wsl so good to know this is an option!
Should I or should not errase the my electronic adress that is in the end of the ssh key when pasting it to GitHub?
So I assume you're talking about your email address which we provided to generate the SSH key. In short, you need to provide the email that GitHub already knows about. This is what GitHub uses to keep track of who made a commit.
But you should know that whatever email you put in there will be public. Thankfully GitHub has a solution; they provide a private email that's associated with your account that you can use. You can then use that private email address for your SSH key.
Here's the official docs on that: docs.github.com/en/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-your-commit-email-address
Hope that's all helpful!
Followed step by step, no matter how many different ways and times I try adding the ssh agent (what you did around 6:10), it either says "No such file or directory" or "invalid format". Any help appreciated!
Hmm, you might want to make sure you have the file created and has the file contents I show exactly written. It'd be my guess that it's the file and not the command (`ssh-add ...`)
Make sure the name and path of the generated file from the `ssh-keygen` step. And then make sure the config file (in the video it was `~/.ssh/config`) references the correct generated file.
It might be helpful to also read through the official GitHub documentation on this: docs.github.com/en/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent
I hope that helps & good luck!!
Very clear instructions, thank you!
Thank you very much! You helped alot. Wish you all the best, subscribed !!!!
You're welcome! And I'm glad the video helped!
Hoping to have more videos up sooner than later (*crossing-fingers*) so thanks for subscribing!
one of the Good explanations...
Thanks! I tried to do it well since I know that a lot of explanations/tutorials are a little lacking for some.
Super helpful tutorial!
A super "thank you"! So good to hear it was helpful!
in 5:52 which button do you to touch save the file
Great question- I explained this in the pinned comment, but in short I'm using vim which requires you to hit `ESC` (on the keyboard) and then type `:wq` before hitting `ENTER`
In retrospect, I should've used a more beginner friendly command line editor but I'm so used to using vim I didn't think much of it when recording the video. Oops 😄
This was very helpful, thank you!
You're welcome! So happy to hear it was helpfuL!
God bless this man.
😇 Thank you! I hope I can keep putting out good stuff, but if I never do, I know that at least this one video has been so helpful to others!
Many thanks. You saved my day.
Yay! Happy it helped you out in your time of need! 😄
thanks for helping with my doubts on this one, however i cant seem to push my folder to my git repo.
the add and the commit has been done, it just isnt pushing, showing me an authentication error
Great video. Can you make a similar tutorial but for adding multiple SSH keys associated with different GitHub accounts?
Thanks! I might but you should know you can simply just do the same process on your computer but just go through the steps with a different GitHub account. If you do it right, your computer should handle it pretty seamlessly 😄
very well explained. thanks for sharing. 🙂
My pleasure!
You are great! Thank you
I want to ask you if you can share the part in the ~/.bashrc that changes the terminal to look like yours , thank you!
Oh I couldn't tell you exactly what I had that I had here (I change my config frequently), but I will tell you it was zsh (not bash)
You might want to check out powerlevel10k for some of the theming I use. Also, this repo for autosuggestions that I found super useful: github.com/zsh-users/zsh-autosuggestions
you saved my day. OMG it worked so well. Thanks a lot! Brilliant~
Yay! So happy to hear I helped saved the day for you :D
This was an very helpful video!!! THANKS!!!
You're welcome! So glad it was helpful!!
incase you get stuck at eval. install wsl and type "bash" in the at the point u had the eval problem. or better still type bash if u already have wsl installed
Thanks for the tip!
I'm definitely a unix-guy myself and I'm less familiar with using Windows. I've also have had luck installing and using Git Bash on Windows
This was very heplful, many thanks :)
Many "you're welcomes" 😄 Good to hear it was so helpful!
Great Job Victor!
Clear and fast tysm you're saving me
yup very neat and clean explanation...❣
Thank you! That means a lot that you found it to be a good explanation!