Just want to say thank you for the great tutorials. I even took a course in udemy to get basic understandings of git but you have explained it really well and made things a lot more clear to me. I really enjoy your enthusiasm and speaking style when doing the tutorials as it is precise and quick and not boring. I look forward to going over your other contents as I am currently studying web development and a complete noob.
I watched some git series from many other places and Honestly, this is the best git tutorial series. it's very organised, detailed and straight-forward. Thank you.
The is a great tutorial series on Git and Github! I've been struggling to get my head around it, but this has really helped me. You're a great teacher. Thank you!
For anybody having trouble during the cloning repo bit (push request after cloning the repo) - Github has changed from master to main as their default branch so the new code would be git push origin main instead of git push origin master :)
thanks so much for the git series. was always looking out for information on this subject. you're illustrative approach in explaining obscure concepts is second to none. thanks v much, Shaun.
This whole tutorial really helped me a lot in too many ways. I really had to thank you. It's actually my first time to even write a comment on youtube.
There were a few git tutorials that i understand a bit as newbie but these tutorial was awesome and I could understand really ALL. You have a great way of presenting, no rubbish, only what is necessary and with examples. I now see that it is already 6 years old and still working well. Thank you very much! I hardly be a subscriber but I've seen other tutorials (other subjects) of you and these were also great, so I SHOULD subscribe and i did.
4:41 What wasn't mentioned here is that if a README file is initialised then it will cause trouble when trying to push files from local repo to GitHub. There are places in the net that described how to workaround this problem but it would've been great if the Net Ninja had mentioned this issue in this video. 12:35 When I CD into the just cloned folder, what follows the folder name is (master -> origin) instead of (master) as seen in the video. I don't know why it's like this.
I got the same issue too. I believe git/github have made some changes whereas it automatically creates an alias (origin) if the repository is cloned, not 100% sure about this though. This comment is months old but for the benefit to those wondering, in my case, I just use main instead of master. Say, you're from a branch and you want to switch to master (main). From a branch, you do 'git checkout main'. The folder will still remain as (master -> origin). And when you're ready to push the files just use 'git push origin'. I hope Net Ninja would clarify this one too as this video might little bit outdated.
If anyone gets an error when trying to push to master, say 'git push origin main' instead. Because as of Oct. 2020, any new repository created in GitHub is created with the default branch named main, not master.
On a side note, for those who have seen git push -u origin main. Essentially, it allows git to track your upstream (push) and downstream (pull) end points. Basically, once you have executed the above command, you do not need to mention origin or main anymore. You can simply execute git push.
For anyone using two-factor authentication (for their GitHub), in order to push your repo you need to use a personal access token for your password instead of your usual password when prompted in the command line (password never shows in the command window for those asking). help.github.com/articles/creating-a-personal-access-token-for-the-command-line/
Thanks for the videos! genuinely excited for the next ones. I have a couple of questions that may or may not be covered in future videos: how do I stop the cmd line asking for my github username and password each time I push my repository? how does saving work when I have cloned someone elses repository, and want to reupload these files to my own repository (for example. not sure if that made sense)? for example I have cloned a javascript workshop repository and if I push it to a remote repository, wouldn't it just be trying to upload my version to the other person's online repo? Thanks!
Try running these before the push command git config --global credential.helper wincred This way, it caches your credentials so you wont have to enter it again. :)
If you're watching this in 2021 and you are unable to push to a repository that you cloned from GitHub to your local, it is because "master" was replaced by "main". So do git push origin main EDIT: Make sure that Github and your local repository are consistent with the master/main name before pushing or pulling cuz this caused me some headaches
Great tutorial. One question does come to mind. I tried pushing part of one of my sites up to github, but I want to exclude the database-config.php file for obvious reasons. I'd also like to exclude some heavy media directories as well. I tried setting up a .gitignore file, and did the -rm cache thing. However, even after creating a new branch and pushing from there I still wind up with the whole kitchen sink, instead of the one little applet.
To any and everyone having trouble entering their password when the prompt for your github username and password shows, just type them as normal. Git does not show any indication that the password is being typed, but it is processing it. So just type your password and it should work.
Brilliant dude, you are awesome !!!! Thanks for the very nice tutorial. You know what before searching any topic on Google or taking any course at udemy or edureka, I am looking first @Ninja, because you are best
I didn't even realize you could start on the git, get your files in order, then add, commit, merge, etc. And then create a repo on Github. I always thought you had to create a repo first on Github, then you would be allowed to use git commands.
I noticed @13.15 locally after you cloned the remote, you added a new index file - gave it title of crap portfolio and saved it but the repo didn't notify of any changes? You couldn't see in the tree because the project directory was closed but in cmder (master) was still white
Thank you soo much for all the things you are sharing and I'm sorry but I would really want to get in touch with you cuz I'm having some troubles with the github Whenever i try to apload the files by using git push It gives me some github panel to login then some fatal error message telling me to enter username and password in cmder panel but the password line doesn't accept anything it stays empty, Sorry i had to lot of words cuz I'm not so good with English And thanks again
Can someone who's already made a project and pushed it to github clone their own repository and work on it or should they just make a branch and merge it later
When pushing to the remotely created portfolio, I had to run `git push` instead of `git push origin master`. I was getting an error 'src refspec master does not match any`.
Thanks for our great hero again the super Shaun ! For the guys who faced the username and password problem here is the solution: -run this cmd : git remote set-url origin git@github.com:username/repo.git and it's gonna work great
Following the instructions that you told, I receieve this "fatal: The current branch master has no upstream branch" when i try do the push command. How to fix this?
i have a question. if we're using git, its edited on our local machine? how can some other devs work on it and interupt the main branch / faeture 3 branch if they merge together?
I got (main -> origin) on the second method with readme file and I got to do " git push origin main " not master, I checked and I got 'main' branch in the repository. Why? sth changed in github? When I was installing git there was info that a lot of comapnies replaced name 'master' to 'main' or sth like that. There were other names 'truck and etc.
Awesome tutorial series, many thanks! However, when I try to push my repository to github, it asks me for my username and password. I can input my username, but when I try to input my password no text shows up at all. Can anyone help?
@@omgh8287 I think the password simply doesn't show (which is a pain), not even the usual password dots. just try inputting it normally and pressing enter, it should work
@@g-radiation7154 Like you suggested i just typed in the password (which didn't show) upon being prompted and I was able to push my repo to github. Thanks for the suggestion!
The best github tutorial series in the whole universe....
Haha, thank you so much :)
true af
I now know
This is spot on correct !! Best Github tutorial in the universe !!
true
Hands down the best Github series ever. Even after 5-6 years, no better tutorial series have been produced
6 years later and you're still helping out with your github series. Now everything about git and github is now coming together
Just want to say thank you for the great tutorials. I even took a course in udemy to get basic understandings of git but you have explained it really well and made things a lot more clear to me. I really enjoy your enthusiasm and speaking style when doing the tutorials as it is precise and quick and not boring. I look forward to going over your other contents as I am currently studying web development and a complete noob.
Awesome, thanks so much - really happy you liked! I hope you enjoy my other playlists too :D
I watched some git series from many other places and Honestly, this is the best git tutorial series. it's very organised, detailed and straight-forward. Thank you.
Thanks :). Glad you liked it.
he is not ninja for nothing
6 years later and still the best tutorial for git and github
Thanks! :) that's awesome
Most detailed and easy to follow-up Git tutorial on UA-cam, hands down
The is a great tutorial series on Git and Github! I've been struggling to get my head around it, but this has really helped me. You're a great teacher. Thank you!
For anybody having trouble during the cloning repo bit (push request after cloning the repo) - Github has changed from master to main as their default branch so the new code would be
git push origin main
instead of git push origin master :)
great :/
thx for this; rlly helped me out!
This beats every other github tutorial on the internet. Simple, straightforward and on point. Efficient just like a NiNJA.
thanks so much for the git series. was always looking out for information on this subject. you're illustrative approach in explaining obscure concepts is second to none. thanks v much, Shaun.
Thanks so much :). Really glad you like!
binge watched the entire playlist.. i love how concise it was without missing the important explanations. Thank you Shaun! :)
Thanks again. I like the way you break up content into manageable chucks that can be swallowed in one short sitting. Great!
This whole tutorial really helped me a lot in too many ways. I really had to thank you. It's actually my first time to even write a comment on youtube.
Thanks so much :)
I've watched so many videos in UA-cam but this whole playlist is the best toturial i've ever seen.
That means a lot, thank you :)
There were a few git tutorials that i understand a bit as newbie but these tutorial was awesome and I could understand really ALL. You have a great way of presenting, no rubbish, only what is necessary and with examples. I now see that it is already 6 years old and still working well. Thank you very much! I hardly be a subscriber but I've seen other tutorials (other subjects) of you and these were also great, so I SHOULD subscribe and i did.
You're a legend
You have nothing to hide, ninja. All boil down to these ttutorial thankss.
This was a great video. I'm a newbie and your presentation was straight forward and easily digestible.
Really glad you like it 😀
Wooow 6 years down but the course is still the best
Amazing content! I just love how you explain everything because the way you present information is very intuitive and easy to understand!
I've just started using Git at work, so these are really useful, keep it up!
Glad they can help, good luck learning :)
this is best GitHub and git tutorial I ever seen , thanks a lot man, you're a good man, pleas have a nice day
Thanks so much! You too :D
so crucial. I'd been wondering how this stuff worked for so long.
I found all your git tutorials super awesome..
I've been trying to learn how to use Github and was running scared when I received conflicts. Thank you so much for the elaborate explanation.
4:41 What wasn't mentioned here is that if a README file is initialised then it will cause trouble when trying to push files from local repo to GitHub. There are places in the net that described how to workaround this problem but it would've been great if the Net Ninja had mentioned this issue in this video.
12:35 When I CD into the just cloned folder, what follows the folder name is (master -> origin) instead of (master) as seen in the video. I don't know why it's like this.
I got the same issue too. I believe git/github have made some changes whereas it automatically creates an alias (origin) if the repository is cloned, not 100% sure about this though. This comment is months old but for the benefit to those wondering, in my case, I just use main instead of master. Say, you're from a branch and you want to switch to master (main). From a branch, you do 'git checkout main'. The folder will still remain as (master -> origin).
And when you're ready to push the files just use 'git push origin'. I hope Net Ninja would clarify this one too as this video might little bit outdated.
same here
i got the name main -> origin
Appreciate your work man! Thank You :). This series should really have much more views.
Awesome, I'm excited about the next lesson already!
If anyone gets an error when trying to push to master, say 'git push origin main' instead. Because as of Oct. 2020, any new repository created in GitHub is created with the default branch named main, not master.
Great Series! I could understand everything without a problem. Gotta look out for more courses from you. Cheers!
On a side note, for those who have seen git push -u origin main. Essentially, it allows git to track your upstream (push) and downstream (pull) end points. Basically, once you have executed the above command, you do not need to mention origin or main anymore. You can simply execute git push.
Thank you for making such a wonderful video tutorial. Best tutorial on git and Github.
This is the greatest ever tutorial of git. Thank you so much.
best git and GitHub tutorial ever good job man !!
Thnx. This is the best git tutorial I've seen so far
For anyone using two-factor authentication (for their GitHub), in order to push your repo you need to use a personal access token for your password instead of your usual password when prompted in the command line (password never shows in the command window for those asking).
help.github.com/articles/creating-a-personal-access-token-for-the-command-line/
Sir, you make me feel empowered ...Very gratefullll
Best tutorial in the world , loved it
thanks, team. I was stuck one adding files to the same repo after week/month. this video solved it.
thanks
Great content. Keep it up!
This is exactly what I was looking for. Thanks Shaun!
it's been years, but still useful thanks,
hands down the best tutorial out there!
But which tutorial contains the git ignore part?
Nice tutorial Shawn, thank you man!
I´m still going back to this video to see how to push code to github :D :D :D
World class level tutorials!
Amazing tutorial. Many many compliments!
Very clear explanation. Thanks
Thanks for the videos! genuinely excited for the next ones.
I have a couple of questions that may or may not be covered in future videos:
how do I stop the cmd line asking for my github username and password each time I push my repository?
how does saving work when I have cloned someone elses repository, and want to reupload these files to my own repository (for example. not sure if that made sense)? for example I have cloned a javascript workshop repository and if I push it to a remote repository, wouldn't it just be trying to upload my version to the other person's online repo?
Thanks!
Try running these before the push command
git config --global credential.helper wincred
This way, it caches your credentials so you wont have to enter it again. :)
Very helpful video, thanks 👍
thank you very much for these tutorials!
Kudos! Fantastic explanation.
Another great series, thank you
Glad you enjoyed it :) thanks Malcolm!
Thanks!
Thanks for your support David! :) much appreciated
Awesome Tutorial ! Saviour :)
Really a Ninja 😁👍 Thank you so much!
Thank you so much for this content Sensei:)
very clearly explained
Amazing work but as of now, private repos are free. You can only add up to 3 collaborators though
Great tutorial, it helps a lot!
thanks for your great videos on UA-cam.
Is there a way to merge manually and decide line by line which code you want to merge into your master?
Really Helped me. Thanks a ton
If you're watching this in 2021 and you are unable to push to a repository that you cloned from GitHub to your local, it is because "master" was replaced by "main".
So do
git push origin main
EDIT: Make sure that Github and your local repository are consistent with the master/main name before pushing or pulling cuz this caused me some headaches
Thanks for this tutorials they help a lot!!! It's the same procedure for GitLab ? and what about if we want to do it with the SSH key , how we do it?
Great tutorial.
One question does come to mind.
I tried pushing part of one of my sites up to github, but I want to exclude the database-config.php file for obvious reasons. I'd also like to exclude some heavy media directories as well.
I tried setting up a .gitignore file, and did the -rm cache thing.
However, even after creating a new branch and pushing from there I still wind up with the whole kitchen sink, instead of the one little applet.
To any and everyone having trouble entering their password when the prompt for your github username and password shows, just type them as normal. Git does not show any indication that the password is being typed, but it is processing it. So just type your password and it should work.
thank to the best serie..it was really helpfull for me to understand the git :)
Glad to hear that! :) thanks for watching
Brilliant dude, you are awesome !!!! Thanks for the very nice tutorial. You know what before searching any topic on Google or taking any course at udemy or edureka, I am looking first @Ninja, because you are best
oh cool found the github part , thx
Thank u so much sir for this great tutorial.
simply awesome.
First good job. Second, you don’t mention authentication in this series either SSH or HHTP. Would love to better understand this aspect.
I didn't even realize you could start on the git, get your files in order, then add, commit, merge, etc. And then create a repo on Github. I always thought you had to create a repo first on Github, then you would be allowed to use git commands.
I noticed @13.15 locally after you cloned the remote, you added a new index file - gave it title of crap portfolio and saved it but the repo didn't notify of any changes? You couldn't see in the tree because the project directory was closed but in cmder (master) was still white
thank you so much sir
Brilliant!
in the clone instead of creating a folder manual. let's say your using vuejs. can you use the npm install -g @vue/cli?
I think there is a typo in the title of that video : Gilt => Git
well spotted :). Will change now. Thanks.
love from nepal
Thank you soo much for all the things you are sharing and I'm sorry but I would really want to get in touch with you cuz I'm having some troubles with the github
Whenever i try to apload the files by using git push
It gives me some github panel to login then some fatal error message telling me to enter username and password in cmder panel but the password line doesn't accept anything it stays empty,
Sorry i had to lot of words cuz I'm not so good with English
And thanks again
6:22 Is it true that I can push my repo to any github as long as I have the url ??
same accent Tomas Shelby spoke
Can someone who's already made a project and pushed it to github clone their own repository and work on it or should they just make a branch and merge it later
Thank you!
Thank you sir...
Thanks for watching!
Say i pull the changes from the master everytime before i do my changes, there will be no conflics ?
thank you shaun
Thanks for watching! :)
thank you sir
When pushing to the remotely created portfolio, I had to run `git push` instead of `git push origin master`. I was getting an error 'src refspec master does not match any`.
Thanks for our great hero again the super Shaun ! For the guys who faced the username and password problem here is the solution: -run this cmd : git remote set-url origin git@github.com:username/repo.git and it's gonna work great
Following the instructions that you told, I receieve this "fatal: The current branch master has no upstream branch" when i try do the push command. How to fix this?
i have a question. if we're using git, its edited on our local machine? how can some other devs work on it and interupt the main branch / faeture 3 branch if they merge together?
what browser are you using?
Every time I use 'git push url master' command, Cmder asks for my username and password. Is it possible to not sign in each time I use time command?
Love you shaun
Awesome video
but my the git push always request username and password
bro predicting remote job 5 years back.
I got (main -> origin) on the second method with readme file and I got to do " git push origin main " not master, I checked and I got 'main' branch in the repository. Why? sth changed in github? When I was installing git there was info that a lot of comapnies replaced name 'master' to 'main' or sth like that. There were other names 'truck and etc.
F.Fantasticcc ! ! ! !
Awesome tutorial series, many thanks! However, when I try to push my repository to github, it asks me for my username and password. I can input my username, but when I try to input my password no text shows up at all. Can anyone help?
I am having the same problem. Did you find a fix for it ?
@@omgh8287 I think the password simply doesn't show (which is a pain), not even the usual password dots. just try inputting it normally and pressing enter, it should work
@@g-radiation7154 Like you suggested i just typed in the password (which didn't show) upon being prompted and I was able to push my repo to github. Thanks for the suggestion!