Build software better, together

2 min read Original article ↗

Smart PR reviews

Is a recently hired engineer review the same as your CTO's review?
Does a typo fix require the same effort to review as a 1000 line breaking change?

Weighted Reviews allows your team to require review points instead of # of reviews.

Features

  1. Require a default points per PR, per repo and per org. Change a PR's required points with just a comment.

  2. Assign per org and per repo review points. Example:

    • Default: 40 points per review.
    • CTO: 70 points per review
    • Lead engineer: 50 points per review
    • Senior engineer: 40 points per review
    • Engineer: 30 points per review
    • New engineer: 10 points
  3. Require different points per semantic commit type / number of changes SOON

Setup

  1. Install the app in your user/organization.
  2. Use protected branches with 1 required review.
  3. Once you receive the first commit status in any PR, require Weighted Reviews check in your protected branches configuration.

Starting config: each PR needs 100 points and each review counts as 100 points.

Configuration

On any pull request where WR is active, comment /wr (e.g. \wr require 200) with one of the following commands:

Command Description
require [points] Set required points for this pull request
require-repo [points] Set required points for this repo (doesn't affect PR)
require-global [points] Set required points globally for user/org (doesn't affect PR)
reviews-repo [points] Set default points per review for this repo (doesn't affect PR)
reviews-global [points] Set default points per review for user/org (doesn't affect PR)
reviews-repo [points] user1,user2,.. Set points per review for specified users in this repo
reviews-global [points] user1,user2,.. Set points per review for specified users in user/org level

NOTE: you can send multiple commands in the same comment, 1 per line.

Support, Feedback & Suggestions

Please contact me at wr@diegorbaquero.com