First, let’s admit it: reviewing pull requests is really hard. As a reviewer, it’s your responsibility to make sure that the code is correct and of high quality before it gets merged into master. You are expected to do that by looking at a diff and list of files changed. You have to understand what the pull request is trying to achieve, what approach is being taken, what’s going on, and how all these files fit together — enough that you could potentially suggest an improvement. You may have to be on the lookout for typos or style problems. That’s a LOT of stuff a reviewer needs to do, especially in a large pull request!

I started to create understandable PRs since I started contributing to Sustainable Educational Foundation — SEF in late 2019. For those who don’t know about SEF please make sure to visit our site to know more details. In a nutshell, At SEF, we have something in store for everyone especially you are a student, expert, or a volunteer. After starting contributing to SEF I realised the importance of a quality PR and today I’m going to share those qualities with you.

#pull-request #branch #github #gitlab #git

How to Create Pull Requests That Reviewers Understand?
1.15 GEEK