Code Review process

Code Review is indeed a critical process during software development. Among different types of processes that can exist for doing software development and code reviewing, I'd like to highlight some, here.

This one (image below) might be very well known among many developers. Create another branch for development, work there all changes and updates, and... pull request

Pull requests let you tell others about changes you've pushed to a branch in a repository on GitHub. Once a pull request is opened, you can discuss and review the potential changes with collaborators and add follow-up commits before your changes are merged into the base branch. source: Docs GitHub

Once you are noted by the team (or reviewer) about the pull request, there is the "Code Reviews" and "Commits"
All those reviews and checks are very important just before merging to the master branch.

Image Reference

Remember, that avoiding (forgetting, ignoring,...) code review can help adding more and more to your technical debt. (Read here for more info about tech debt)

Let's check one more example:

Image reference

What I like from the example above is the importance of "peer review" and "automated review process".
We should not forget the importance of team work during the software development process. Also, "automating" the coding review helps you learn more about your coding style as well as remembering good coding practices for a great software project legacy.

I know there are other plenty processes for software development and code review that might also be customized for each team, project, etc. What is your process?

Psss, for automated code review, check out Code Inspector to get started for free analyzing your code quality and calculating your tech debt in your projects at GitHub or GitLab or BitBucket.