Well for someone slower like me, it would be good practice even if I get to the end and find out someone else already submitted a PR. Might even learn from comparing their PR to my code.

This has been a great course. I learned a few things about Git and GitHub that I didn't know, but the parts about proper communication with the maintainer, adhering to the projects code style, and a good, clean, accurate PR description are pure gold.

My take away from the course is:

Be meticulous, and methodical.

Be mature and professional.

Keep it simple but clear and accurate.

Don't tag a maintainer by name until after they have initiated a conversation/request.

Keep an open mind and see things from the maintainers point of view.

Keep the description up to date and accurate with the actual end result changes of the PR

Squash duplicate commits (don't be annoying)

Last but not least, study the existing project and understand how it works and what testing, code analysis, and standards are already used in the project before starting and use them in your PR.

So What's Next?