 G'day all, our Robert's here. I'm gonna show you what it looks like to get a pull request So at the end of doing the workshop Or if you're contributing to any open-source project, probably the last step is to put in a pull request to the maintainer to have your changes included And so if I'm being the maintainer, which I'm kind of in this case, I suppose This is my main interface to get Changes from other people to get input contributions from other people It would be great if I could just open up the repository by access to everybody and let them go and do what they wanted but That becomes unworkable And in particular I guess programmers have learned over the years that at this stage of when one programmer has finished all their work and thinks It's great passing it off to another programmer for review is a good idea And that's really what a pull request is. It's a review That a second set of eyes makes before they bring that working code Into what's called master the main The main line of the repository so that everybody else can use it as well It also gives that maintainer a chance to Deal with any clashes of multiple people working on multiple things, but I'm just gonna show you what it looks like So I've got the mini console code here on the left in this lovely shade of blue that I'm experimenting with at the moment Now the filing question I think I can have a look and then the pull request on bitbucket just appears like this really nice interface This is something that github and bitbucket pulled along that didn't exist really without them Not is it built now? It's not built into the What I can now request changes very nice So bitbuckets obviously introduced some new features So this what happens when you're pushing and pulling changes between forks instead of pushing important changes between branches or working copies So what it shows me is all of the changes that were made I can see Who made it and I can see their commit Comments that they put in I can see each of the three commits That came in one two three. They all kind of get bundled up together For me to look at and Then I've been out as a reviewer so you can see I'm here is being able to review it Look at this There's lots of little I can put comments directly on a line if I want to send the pull request back To the developer Send that back and say no no no please do it this way and then they can send me another pull request Here's an example of what I see. It's just looking that changed. It's really useful All they did was change the background from zero to 45 on 66 to 23 interesting Here I can see I've also changed some of the flame colors From these three the red ones are gone and the green ones are in We've got two different colors for whether the warp drives on and they pick some different colors Now I can't see here what those new colors look like But in my mind I can my mind's eye. I can see that I'm happy. So that's obviously a change from white to yellow Yes, that's good. So those are the three changes kind of bundled together And I can see all the changes that come from the Pull request and I can decide whether they're good or not and normally what I will do in In a real project Is I'll get myself a copy of this version and run it on my own computer And in fact in bigger projects This would be set up to automatically run against the continuation integration tests And I would have had up the top here a ticker across to tell me whether it passed the tests or not But we're not quite at that level of sophistication with this, but I can look at them and decide Yep, I like those and I approve them Okay, now that was just me being a reviewer approving the requests There's a separate step to get the pull requests brought over So let's see if I can remind myself of exactly where that is So there's an accept button. I think oh there you go merge okay, so It includes some automatic comments for me before it goes into master You can merge that across And it was kind of my job to make sure that merge wouldn't have gone wrong Although we can set up again continuous integration things to test that the merge Couldn't have gone wrong So hopefully if I go back to commits now I will see There we go You can see that the new commits from sophie have come in It looks like there was one that I made In between when she made hers that needed merging, but it's all merged back up here to the point So she put in one two three one two one two three that merged one and then the last bunch was the The pull request coming into even though I clicked the button to see off because they all have all And over here I should now be able to pull this. So let's just get up to our file Lock it by Java and go to a section where we're going to see those colors There's a background so that'll be up in the start of draw. There we go background zero So if I jump over to the get part of visual studio because I'm doing this on my desktop And pull but the same thing happens if you're doing it on terminal bam, you can see it's updated straight away So yeah, that pull request went through I can merge it and write it on my own computer now Okay, that was all I wanted to say See you next time