How to Review a Pull Request on GitHub

Reviewing a PR on GitHub is an activity we do daily, hence having good knowledge of the tool increases our efficiency and ensures smooth collaboration with our colleagues. In this beginner's guide, we'll explore the core features GitHub offers and some practical tips to enjoy the process. Conducting a code review is actually a really tough task, it not only requires programming knowledge but also a strong cultural maturity, for instance when it comes to criticizing the code and not the author. Empathy is among the hardest skills one has to master, but knowing the tool is one of the first steps in making the process easier. _______________________________ Hit like and subscribe for more content! :D Beginner-Friendly Open Source Projects: https://github.com/DevLeonardoCommunity Join the Discord community! Here's the invite: https://discord.gg/bqwyEa6We6 You can also follow me on the other platforms: Twitter: https://twitter.com/Balastrong dev.to: https://dev.to/balastrong GitHub: https://github.com/Balastrong Home: https://leonardomontini.dev/ TikTok: https://www.tiktok.com/@balastrong Instagram: https://www.instagram.com/devbalastrong/ TIMESTAMPS 00:00 Don’t use "add single comment" 00:35 Pull Request Data 01:07 Commits & Pipelines 01:32 File changed tab 02:09 Adding comments 03:00 Start review 03:36 Multi-lines comment 03:55 Finish the review (Approve, Request changes or Comment) 04:50 Reply to a review & accept suggestions 06:13 Review additional changes 07:09 Finalizing the review 07:44 Review from Visual Studio Code