Getting a Pull Request Merged and Wrapping up

[00:00] Our pull request has been merged. It's time to celebrate.

[00:03] Let's take a look at the commit history to make sure that our commit is in there. We can see that our commit is here, but we'll also notice this merge commit here.

[00:11] When the project maintainer clicks the green merge button, GitHub runs a git merge command, but it adds a flag to the command which essentially forces a new commit to be created for the merge. Never fear, though. Your work is in the project as you made it.

[00:24] Now, let's look at the contributors graph. For this project, I actually am the only one who's made any changes, but after your pull request is merged you'll see a card representing your contributions, as well.

[00:34] That's our series. I hope you enjoyed it.

[00:36] Before we wrap up, I want to say that most of the Git commands that we have executed in this series are just one way to accomplish the same task. Git is a huge subject which I am unable to cover in depth for this series.

[00:48] There are many ways to do the same thing in Git, so I recommend you spend some time learning this ubiquitous source control management software.

[00:55] I also want to invite you to contribute to this repository, stack-overflow-copy-paste if you want to try this out. I don't expect anyone to actually use this module, but if you want to have a friendly place to practice feel free to file issues and pull requests. I would be more than happy to give you direction.

[01:12] Thank you for watching this series.