Branches - Git for Android Developers - Part 4

In this video you will learn about the concept of branches in Git.

⭐ Get certificates for your future job
⭐ Save countless hours of time
⭐ 100% money back guarantee for 30 days
⭐ Become a professional Android developer now:

[Hrit]

Have to say this is a very underrated playlist for git. I would recommend this playlist to anyone trying to learn git in general and not just to Android Developers.

[iamnikhilmehta]

The way you have made the Coroutines playlist, are you planning to make playlist on "Kotlin Flow"? That is a very hot topic and awesome API also.

[martinhalus]

I just love I can always return back to your guidelines after week, month, half-year to re-fresh knowledge!

[cagrkrt]

This channel is priceless. Thank for the effort

[abhirajsachan]

i was always afraid of git . but now i am loving it . thankx man

[preraksemwal]

very underrated video. Great explanation.

[scottloewke]

The yellow and green symbols are tags (each looks like a price tag, for example). They are not the same as Git tags, however. Instead, they represent branch pointers. A branch pointer is the "tip commit" (i.e., the most-recent commit on the branch), and they have an associated branch name next to them. If a bunch of them are grouped closely together, you can click on the group to see a popup window detailing which branches they represent.

The yellow tag indicates the HEAD commit, which quickly tells us which branch is currently active (i.e., checked out).

The merge strategy chosen by Git depends on what has happened to the main branch after a branch was created. For example, if you create a bug fix branch off the main branch, make some commits on it and then merge the bug fix branch into the main branch, the kind of merge strategy used will depend on whether commits were made on the main branch after the base commit (i.e., the commit your bug fix branch is based on). If no changes were made on main since you branched, then a "fast-forward" merge will be done. It just adds your bug fix branch's commits to main rather than actually merging any code, since there's no possibility of conflicts arising. On the other hand, if commits were also made on main after you created your bug fix branch, then the possibility of merge conflicts exists. In this case, an "auto-merge" is done, to the best of Git's ability, using the "recursive" merge strategy.

[devetips]

yeah master now called main ....masterful of android thank you

[mahmuduulkarimlincoln]

brother. every video you make... you can cover the most important topics in minimum time. that's you brother....thank a lot for making our life easier.

[shadabkhan-fbvt]

Great information sir it helps me a lot in my project

[anitakrizzan]

Thank you for making the amazing videos.

[udayakrishnalekkala]

You are awesome bro. You made complex simple

[melianiabdelghani]

very amazing channel thank you for your videos :)

[nithinrupireddy]

You are doing great work bro. Keep going❤✔

[amineayachi]

You should take a look on git flow it help you to correctly manage your branches i learned a lot from this play list hope that youre doing well philipp a lot of thanks

[AlgeriaHere]

Thank you for the video, very helpful

[thedev]

Leaving a comment, so the mighty algorithm gets easier on you :D

[mehulbisht]

nice to see that ad at the beginning and not at the end

[kayax]

Hi, how can we check whether the version of a project in AS is newer or older then the one in github? thanks

[abhiculous]

I have 4 gmail accounts and I hav subscribed you from all of them