Okay, we are continue to explore how to merge books. It's no exact all of the comments, I'll show you later. mostly focus it to merge them into the car. And the current range will be updated to reflect the merge. But target branch will be completely. Again, it means that the promotion is often used together with good Chicago or selected as the current branch.

Then you want to merge and then use get branch minus d for delete and select pinch. But I'll advise you if you're not very confident in your changes, sometimes so it's pretty useful. So, not delete your topic branch quickly. So you can just take some time explore how your changes feathers in the codebase and then you decide you can run it branch on the state and delete it. It's pretty useful sometimes if you worried about membrane get caught on range. So you can like to be a pro over your changes and make some updates and then merge two bench together.

Okay, how big mush works with Nashville combine multiple sequences of commits from different histories into one history and is the most frequent use cases get merge sharp combines two branches together and below mostly talk about how easy is it for combining on the two branches. It will be our main goal to explore these and the scenarios it takes to permit pointers from different branches. And usually it's branch tips like the last changes that you have in your get history at different branches and you'll find the common base common between them. If it's enough as a slide more, we'll talk about examples and how to execute