Skip to content

Latest commit

 

History

History
40 lines (20 loc) · 1.33 KB

pull-request-review-guidelines.md

File metadata and controls

40 lines (20 loc) · 1.33 KB

Pull Request Review Guidelines

Please, use this guidelines as a recommendation for pull requests reviewing.

Reviewer Guidelines

  1. Checkout the branch and run the project locally to see all the changes live.

  2. Check for unit and integration tests. If you accept the PR, then you are in charge of adding tests for the author ;)

  3. Run unit and integration tests.

  4. Try to finish all relevant PR reviews before lunch (13:00).

  5. Try to make an in-person reviews. If the author is free, ask him to sit and go through all the comments together.

  6. Leave meaningful comments even if you make an in-person review with PR's author. In this case other reviewer will know the result of your discussions.

  7. Leave a resolution comments like LGTM, Ship it!, Fix issues and merge.

Author Guidelines

  1. If your PR is blocking you from furhter progress, send a direct message to all relevant Reviewers via Slack.

  2. Think about good and clear PR description.

  3. Mention all those people who must see the PR with github mentions: @reviewer.

  4. If you see a comment like Fix issues & merge, then you are free to merge the changes yourself after fixing all the issues.

Merging policy

The last reviewer merges the changes, unless it is explicitly stated that author should fix commented issues or merge the PR himself.