Open Source Contributions: Start to Finish (Part 3)

Contributing to an open source project is a win-win. You'll be giving to developers and gaining
new experiences in the process. But the process itself can be daunting. How do you show that
you're one of the cool kids, too? It can be easy to go ahead and contribute without finding out
how to best go about it.

The general format for contribution is as follows:

1. Find a bug or a project you'd like to contribute to.
2. Find the project's repository from the main page of the project.
4. If you found a bug, first put it in the issue tracker and discuss it.
Otherwise, investigate the bug further until you feel confident that you can
reproduce and fix the bug.
5. Get a development environment set up to reproduce & fix the bug. This may be
the most time-consuming and irritating step.
6. Fork the latest commit of the main repository to your own local repository.
7. Fix the bug!
8. Commit your code to a seperate branch.
9. Push the branch to your remote forked repository.
10. Create a PR. Ensure to include as many details as necessary. It's helpful
to include a link to the bug in question.
11. Wait for maintainer response.

You can watch part 1 here: https://www.bitchute.com/video/45EoUqQJqQRg/

You can watch part 2 here: https://www.bitchute.com/video/iJ4VJNFZ4n9m/

In this part (part 3), I follow up on the code author's response, verify the PR, and
close the branch and my fork. That's basically the end of it.

At the time of the writing the branch was merged into the main master branch.

If you found this video helpful, please say so down below.