I watche some videos that are more longer than this, just by reason to find more details and practices to undertand, but when i watch this video i change my thought , it's wonderful short and has more practice and details , also the english its clear for beginners , good job men you'r aweson , keep going i appreciate .
I didn't learn a lot as I am somewhat past the noob stage. But, this is an excellent video and did help solidify some of my knowledge and I will most definitely use this video to help explain for others. Very good. Good combination of speech, text and graphics (as always).
@@awesome-coding I do enjoy all of your videos. I do like how you move along quite quickly actually but never at the expense of missing information. I think that has to do with the combinations of word, graphics, code and so on. I think it isn't easy to get that combination right in so succinct and thorough a manner. Well done. Please do continue.
one big gotcha to look out for and you stated it but you should empahaize is "git branch" by itself makes the branch based off your current branch I cannot tell you how many devs make a feature-one branch, then make feature-two and now it is based off of feature-one when they probably meant to do main I recommend getting used to checking where you are before making branches (i also exclusively use git checkout -b new-branch source-branch)
@@awesome-coding Man! you are incredible; most youtubers would've glossed over it, but you decided to take the extra effort to make the correction. Appreciate it✌🎉
1:19 shouldn't this be the other way around? Git doesn't take a snapshot of the entire working directory, ie the project, but works on file changes/diffs At most the phrasing here is misleading
Great job! This might be the easiest video to learn Git. I often end up creating garbage commit messages after feeling mentally exhausted. Do you have any tips for improving this?
Hey! Thanks for the feedback! When working on a new feature, just use a feature branch. You can add whatever messages you want in there. I usually do this as well, and I just use the "fix" or "commit" message whenever pushing on that feature branch. Then, when the feature is ready to be merged back into main, I do a squash commit (just like I mentioned in the video), and that squash commit receives a meaningful name (like the Feature name and details for instance). After the squash merge, the history will show only this last message, and will discard your "garbage" messages. Hope this helps!
@@awesome-coding Thank you for the advice! That makes a lot of sense. I'll definitely try using feature branches and squash commits to clean up my commit history. Thanks again for the tips and the great video!
So I cant believe i have understood this by working with it for 2 years. One tip I would give is Dont use git reset --hard without pushing the code to remote branch. For adding the files just use the staging + icon in vs code.
@@awesome-coding there was a video 3 days ago about facebook using Mercurial instead of git, prime put up a poll asking how many don't know git, and a huge number of people said they don't know.. prime planning to do a 6h stream with frontend masters clear every doubt of everyone about git...
@vaisakhkm783 ah, got it :)) believe it or not it is just a coincidence.. My video took two weeks to produce, so it was planned and worked on way before prime posted the FB mercurial video.
90% of git usage in small projects - git add, commit, push
The other 10% is what is killing us :))
@@awesome-coding Literal truth
you got it
I swear you need to collab with Fireship, you are amazing tutors
😅 Thanks!
Nope, He is doing much better alone by himself only..
Fireship is nothing but a collection of crap AI videos these days.
@xtraszone I wouldn't mind some of those insane view counts though 😅
@@awesome-coding That is also Correct Bro 😆
if I am not wrong, he already collab with Deno
This has got to be one of the best made, most well-explained educational videos I have ever watched
Thank you! It really means a lot!
I watche some videos that are more longer than this, just by reason to find more details and practices to undertand, but when i watch this video i change my thought , it's wonderful short and has more practice and details , also the english its clear for beginners , good job men you'r aweson , keep going i appreciate .
Thank you!
I didn't learn a lot as I am somewhat past the noob stage. But, this is an excellent video and did help solidify some of my knowledge and I will most definitely use this video to help explain for others. Very good. Good combination of speech, text and graphics (as always).
Glad you enjoyed it! This is one of the videos I worked the most on.
@@awesome-coding I do enjoy all of your videos. I do like how you move along quite quickly actually but never at the expense of missing information. I think that has to do with the combinations of word, graphics, code and so on. I think it isn't easy to get that combination right in so succinct and thorough a manner. Well done. Please do continue.
The best git video ever. Thanks dude!
Thank you!
Excellent video, brother. Thank you.
Thank you!
Amazing explanation ❤
Glad you liked it!
Awesome video
Glad you enjoyed it!
How is this channel on 48K subs? very concise and not a single second wasted.
Thank you!
You missed the most important one
$ git blame
Hey... let's not blame anybody!
that's what i need
Glad to hear!
one big gotcha to look out for and you stated it but you should empahaize is "git branch" by itself makes the branch based off your current branch
I cannot tell you how many devs make a feature-one branch, then make feature-two and now it is based off of feature-one when they probably meant to do main
I recommend getting used to checking where you are before making branches (i also exclusively use git checkout -b new-branch source-branch)
Very good point!
heck, i thought you were going to explain how git itself works under the hood
Sorry :( - I changed the title - didn't want it to be misleading
@@awesome-coding Man! you are incredible; most youtubers would've glossed over it, but you decided to take the extra effort to make the correction. Appreciate it✌🎉
1:19 shouldn't this be the other way around? Git doesn't take a snapshot of the entire working directory, ie the project, but works on file changes/diffs
At most the phrasing here is misleading
i only know git init, git add, git commit, the git push to main
You gotta learn some more, GIT is really powerful, especially if you work in teams or on multiple features.
@@StiekemeHenk when things go unright. I just delete the entire project and re upload again 🤣
So basically the first 3 minutes in the video? :D
Ur using Vim as it's part of git commands, I shared this with junior dev and they are getting error on vim
Woops 😑 Didn't think that might be misleading,
Great job! This might be the easiest video to learn Git. I often end up creating garbage commit messages after feeling mentally exhausted. Do you have any tips for improving this?
Hey! Thanks for the feedback!
When working on a new feature, just use a feature branch. You can add whatever messages you want in there. I usually do this as well, and I just use the "fix" or "commit" message whenever pushing on that feature branch.
Then, when the feature is ready to be merged back into main, I do a squash commit (just like I mentioned in the video), and that squash commit receives a meaningful name (like the Feature name and details for instance).
After the squash merge, the history will show only this last message, and will discard your "garbage" messages.
Hope this helps!
@@awesome-coding Thank you for the advice! That makes a lot of sense.
I'll definitely try using feature branches and squash commits to clean up my commit history.
Thanks again for the tips and the great video!
@@ryo_5748 Thank you! Don't hesitate to reach out anytime you have questions!
Good video, but I hate those flashbanks screens that announce next chapter of the video. Please stick to the dark theme in the entire video.
Thanks for the feedback!
cherry-pick ftw
So I cant believe i have understood this by working with it for 2 years.
One tip I would give is
Dont use git reset --hard without pushing the code to remote branch.
For adding the files just use the staging + icon in vs code.
9:36
Vim mentioned
writing :wq to save and exit vim as if :x didn't exist. *look of superiority*
I write :x only to my wife
@@awesome-coding not only awesome, also wholesome!
It's "without further ADO", not "adieu" ;)
You are right - thanks!
bro how you created a folder without Cd to it lmao
😂 good point
:) someone watched ThePrimeagin...
I usually watch him, but I'm not sure what is the correlation here.
@@awesome-coding there was a video 3 days ago about facebook using Mercurial instead of git, prime put up a poll asking how many don't know git, and a huge number of people said they don't know..
prime planning to do a 6h stream with frontend masters clear every doubt of everyone about git...
@vaisakhkm783 ah, got it :)) believe it or not it is just a coincidence.. My video took two weeks to produce, so it was planned and worked on way before prime posted the FB mercurial video.
@@awesome-coding no okk :)
i always understimate work goes into these videos, and when i edit a video, i wonder why i can't make a movie in 1day XD
I know rebase, but I don't care 😤
This is the attitude we need. 😆
😂
why does your voice sound like ai wtf
Probably because I have no soul 🥲
Nice video, but the title is a bit deceitful.
In what way?
@@awesome-coding ha, you changed it
@@neanelu5 yea I ended up changing it because of the low CTR. Btw nice username :))
this was knowing nothing to knowing the bare least neccesary not advance
It's so hard to please you guys :))
@@awesome-coding Don't think about them.