Up and Running with Git Transcripts
Chapter: Teamwork: Open source and Pull Requests
Lecture: Making a change

Login or purchase this course to watch this video and the rest of the course contents.
0:00 Our developer who was over on Windows who saw that Cool repository and forked it.
0:06 They're about ready to get started.
0:07 Meanwhile the original owner of that project over here on the Mac mike.
0:13 C Kennedy, they have no real notification or awareness.
0:16 So if I refresh, if I revisit this page as the owner I can now
0:20 see, oh look someone has started and someone has forked it and you can actually
0:25 click on the little number there and see who has forked it.
0:28 That's pretty cool. So great.
0:30 We know someone has forked it but that's not super important to us.
0:34 So we don't know why they forked it.
0:35 Maybe just make a copy. Maybe they want to contribute.
0:38 Who knows? So there's no real awareness back at this point to the original owner
0:42 So the Windows developer, the outside contributor wants to convert our lizard character that
0:52 is in the rock paper scissors,
0:55 lizard, Spock game to an alligator.
0:58 And they could just open up this project and start working on it.
1:01 But if you change the branch that you forked from and then the original project makes
1:07 some kind of change and you decide you don't want to keep yours too bad,
1:10 you're out of sync. It's like all these weird merge conflicts.
1:13 So just like before we want to create some kind of feature branch for a pull
1:16 request. So we'll come over here and just say lizard to alligator like that.
1:22 Read that branch. We have our lizard to alligator branch and we're going to do
1:27 our changes there as we saw just like the feature branch.
1:33 So our Windows developer likes to work in visual studio code.
1:37 They're going to go open folder to the desktop.
1:40 Open this up like the folder right now.
1:44 They're on the main branch. So let's go ahead and check out The local Lizard
1:49 one. We haven't checked it out to this machine so we can do that.
1:53 Remote branch, pulls it down,
1:54 creates it and we're ready to go.
1:57 All we gotta do is come over here and decide well,
1:59 how are we going to change this?
2:01 Luckily the original developer really factored as well.
2:04 So everything about the players is just in this cool data structure.
2:08 So we come over here and control eight to do find and replace this alligator boom
2:14 All those changes. Let's make a quick change to the version as well just
2:19 to indicate that. And we can just run this file since the entire app is
2:23 just the file. And look here's our alligator.
2:28 And let's just let's just exercise that character.
2:31 We created it. So let's play it alligator.
2:33 They played Spock. We took spock with the alligator.
2:36 We knew the alligator was the right choice.
2:38 All right, we'll try it again.
2:40 Yes, they tried that again.
2:42 They tried the Spock. Thinking we might switch over to something like scissors,
2:46 but no. Oh, the computer took us that time though with the rocks smashed
2:52 the poor alligator. Yes, we won.
2:55 We won. So check this out.
2:58 We're in the branch, lizard.
3:01 We got one change and so on by the way.
3:02 Very cool to see that. So it looks like everything's great.
3:06 Let's go ahead and save this.
3:07 Go to our repository here. And we just wanna put a message stage that one
3:12 change committed. Alright. Our changes are committed.
3:21 If we look over in source tree on our machine,
3:24 we've got are lizard to alligator right there.
3:29 Fantastic. So we've created our feature branch and we've made our proposed change to it
3:36 again so far over here. Still no notifications of anything happening.
3:43 It's just that we've maybe we got some people starring and forking stuff from our repository
3:47 but no notifications because remember we only changed our copy of the hosted repository in
3:54 our account. Not Mike C Kennedy's original.