 Welcome back to the channel. We've been merging and we've done a number of changes to our repository, and now it's time for us to actually see how we can put back changes that we've made to the original repository that we've forked. For example, here our Classic Press Research Master and how we can just bring it back to be the same with our own fork of the project. It is important for us to have both of them when they match up because if we are to make another change, another pull request or another branch, we'll have merge errors on the other side because some of the merges that have been made on this original repository are missing. So there will be a huge disconnect and that's why we need to actually bring that down. So we're going to change directory into Classic Commerce, which is our plug-in folder. In our integrated terminal, we're going to just go in there and start by writing git branch, and then we'll see what branches we are available and which branch we are on, and we want to go to the master. So we'll clear up this to have a clean place and we'll just type out git checkout and then master so that we can go to the master branch. And our message is coming in. We've switched to our master branch and next what we're going to do is actually now pull down that content from the online server from the original repository that we forked. First things first is we're going to add an upstream just like how we did with original. Upstream is going to save our URL so that we don't have to remember it all the time. So we'll do that by adding git remote, add upstream, then we shall add our particular link to our Classic Commerce fork online. Git allows us to store links in our repository and folks we're going to save our URL by typing git remote, add, and then we'll type out the name that we're going to use, which is upstream, and then we shall copy the link from our repository and we shall paste it back into our editor terminal and we shall just paste it in and that will allow us to save the particular upstream that we want and this is the master branch that is available in Classic Commerce. So now we are going to pull down by typing git pull to bring in all those resources of the merged content and so on down onto our local repository. So we're actually ready to, we are ready with our changes on our local repository. So next we shall just type out git push to send the information online to our fork repository and we shall type git push origin master and once we do that the information will go up on the server and we are ready. So once we go back to our online platform through the browser and reload we'll see that the message comes up and says that this branch is even with a Classic Price Research Master and you can actually see right below that message is that we have what kind of changes were made and which fork it was from and we are good to go so we have everything stored, we have everything synced and that's the beauty of open source. So you can develop a product by having other people contribute to it. Thank you for watching. See you next time.