 Welcome back to the channel. Now, one of the things that makes Mentaena happy is seeing a new poor request coming in. It means the project that you are working on is valued and also it means that the project gets to grow. So when you are Mentaena, you will check the poor request that have come in, read the notes and then also just check if you have any tools that you have put in place to check the poor request that come in. Before you merge that poor request, you can check out whether the tests have been run and that everything is okay. So after checking all the tests, it's only good for you to actually add a comment and show that you value the particular poor request that came in or give comments on why that poor request is not going to be merged. But once that is done, the next thing is to hit that good old button to merge the changes that have come in. And so that's why we hit it, we confirm the merge and then that code will be automatically added to our software or our articles that we were writing for our book. So next thing that will go is just open up our repository, our master branch and realize we will see that the changes did come in and the good thing about Git is that you can actually check what was committed. So you can come and see the changes, you can see what was affected and this is the beauty of version control. You're able to always go and review what happened which normally would not happen with any other system. You just have changes that have been added and you don't know where and at what time whatever change happened. So version control makes things a lot better. Thank you for watching. We'll see you in the next video that will talk about how to update your local repository with the upstream that has actually changed.