I was looking for a perfect RUclips channel for a simplified and easy understanding and have seen more than 50 youtube channels and finally happy that i found your channel sir. Thank You so much you filled confidence in me. I am happy to learn.
Nice vid! Some more information for the git newbies out there: 1. HEAD is a shortcut for "the commit this repo is currently checked out to" 2. A git branch is just a pointer to a single commit that can move when actions (merge, checkout, reset, rebase) are taken 3. Branches in git are largely ephemeral -- where they point changes over time and there's no precise record of where any branch has pointed in the past. This is largely not a problem because the true history of the repo lies within commits and their parental relationships. 4. At 10:00, the merge of develop into master is fast-forward, so master just moves from beca713 to 40c841c without the creation of a merge commit. Fast-forward merges happen when there's no divergence in code between the branches being merged. This is atypical (and often not allowed) for merge/pull request workflows.
Hi This may work if you have small co located teams.. but in the larger systems you may not able to control when someone does the checking Hope it helps Thanks
Thank you so much for your appreciation. Thanks a lot. I do have a python playlist, have a look ruclips.net/p/PL_dsdStdDXbqK2e5knrsErF3VpRK3fyO5 All the best for your learning. Thanks 🙏
I was looking for a perfect RUclips channel for a simplified and easy understanding and have seen more than 50 youtube channels and finally happy that i found your channel sir. Thank You so much you filled confidence in me. I am happy to learn.
Thank you so much for your kind comment 🙏
Nice vid! Some more information for the git newbies out there:
1. HEAD is a shortcut for "the commit this repo is currently checked out to"
2. A git branch is just a pointer to a single commit that can move when actions (merge, checkout, reset, rebase) are taken
3. Branches in git are largely ephemeral -- where they point changes over time and there's no precise record of where any branch has pointed in the past. This is largely not a problem because the true history of the repo lies within commits and their parental relationships.
4. At 10:00, the merge of develop into master is fast-forward, so master just moves from beca713 to 40c841c without the creation of a merge commit. Fast-forward merges happen when there's no divergence in code between the branches being merged. This is atypical (and often not allowed) for merge/pull request workflows.
Thanks for your valuable insights 🙏🙏🙏
Thank you so much sir. I have learned a lot and I think I am ready for our exam. You are a blessing❤
Very crisp and super useful video. Very good and simple explanation. Thanks a lot!
Thank you so much for your kind words 🙏
Thank you sir! Very simplified way of explaining
Thank you so much 🙏
Thank you a lot Sir, you simplified the concept and it's ver clear, thans again
Thanks for your comment 🙏
Excellent series of GitHub
I am a student of UWA n your videos is very helpful for learn my concept ty
Thank you so much 🙏
Simple and great explanation.
Thanks 🙏
It very wonderful platform to learn many things thanks lot sir ❤❤
Thank you 🙏
Can't stop watching
Thank You very much
Thanks a lot for taking time out to write the comment.. Thanks again 🙏
@@Cognitive-Programmer can u do further videos on git
Thank you for reaching out.. will definitely consider 🙏
Excellent sir...simple and effective
Thank you so much for your comment
I like your pace.. Thank you for this informative video
Thanks for your comment
we can also use git switch to switch into different branch.
good video to learn heard things in simple way
thank you
Thank you so much 🙏
Dear Sir, How do we delete barnch simultaneously when we push it git ?
Very good explanation!
Thanks for your comment
pls i want you to make a video on flutter_bloc package pls
Sir , your explanation skills are very nice 💚💚, i clearly understood, please sir can you make some more videos on git..
Thanks for your comment & valuable suggestion 🙏
bro you're good. Really good
Thank you so much for your comment
Your video helped me alot
Thank You...If we were to rate videos, I would have given you 5 stars but for now, it is a thumbs up
👍
Thank you so much for your kind words 🙏
thanku so much sir great video understandeble very much
Thanks you so much for watching my video 🙏
Appreciate your efforts sir but why we need to do merge instead we can do push easily.
Many people might be doing the changes simultaneously. hence we need to merge, Hope it helps. Thanks for your comment 🙏
If we take pull before pushing is enough than merging, is not it?
Hi
This may work if you have small co located teams.. but in the larger systems you may not able to control when someone does the checking
Hope it helps
Thanks
If you get time, could you make a video that shows difference between branch merging vs pull and push.
Thank you sir. I love your teaching. It is so simplified. Please i want to learn Python. Put me through.
Thank you so much for your appreciation. Thanks a lot. I do have a python playlist, have a look ruclips.net/p/PL_dsdStdDXbqK2e5knrsErF3VpRK3fyO5
All the best for your learning.
Thanks 🙏
Hican u pls make video on merge and rebase
Thanks for your comment and valuable suggestion 🙏
This was epic.
Thanks for your comment 🙏
Yourexplanatuon is to ood