- Fork a repository
- Create a new feature branch
- Implement a feature and commit
- Pull changes from upstream
- Rebase the feature branch
- Create a pull request via github interface
- Author create a pull request
- A member of the team(reviewer) reviews the pull request. The reviews might make comments about issues. The author should fix those issues and recreate or update his pull request
- The reviewer merges pull request
- Follow code conventions
- Do not review typo fixes or really simple commits
- Keep pull request skinny. If a pull request has lots of logic and it's not possible to split it up, then an author and a reviewer should do code review together.
10 lines of code = 10 issues. 500 lines of code = “looks fine.” Code reviews.
— I Am Devloper (@iamdevloper) November 5, 2013