Code review process flowchart

Code review process flowchart

A worked example to adapt. Rename steps, add branches and owners to match how your team actually works.

flowchart TD
  s(["Author opens pull request"])
  desc["Add description, tests and screenshots"]
  ci["Automated checks run"]
  d1{"Checks green?"}
  fix["Author fixes"]
  asg["Assign reviewer"]
  rev["Reviewer reviews"]
  d2{"Changes requested?"}
  app["Approve"]
  merge["Merge and delete branch"]
  e(["Deploy via pipeline"])
  s --> desc
  desc --> ci
  ci --> d1
  d1 -->|No| fix
  fix --> ci
  d1 -->|Yes| asg
  asg --> rev
  rev --> d2
  d2 -->|Yes| fix
  d2 -->|No| app
  app --> merge
  merge --> e

About this code review process flowchart

A shared code review flow keeps reviews fast and predictable: authors know what to include, reviewers only see changes that already pass automated checks, and the loop for requested changes is explicit.

It pairs with the CI/CD pipeline flowchart, which picks up after merge.

Step by step

1. Prepare. The author explains what changed and why, with tests.
2. Automate. Linting, tests and security checks run before review.
3. Review. A reviewer checks correctness, design and readability.
4. Iterate. Requested changes loop back through checks.
5. Merge. Approved changes merge and the branch is deleted.

How to make it in flow-chart.io

1. Start from the example. Edit the text in the generator box above so it names your own repository rules and checks, then press Generate. The free preview needs no sign-up.
2. Add the branches. Add the decision points that matter for you, for example two approvals for sensitive code? or design review. Each decision becomes a diamond with labeled outcomes.
3. Assign owners. Save the diagram to the editor (free account) and rename steps to show who does what: author, reviewer and CI.
4. Share or export. Share a read-only view link: people with the link can view the diagram but not edit it. Downloads as PNG, SVG or PDF are part of Flow Pro (see pricing).

Tips

• Keep pull requests small enough to review in one sitting.
• Set a review response target.
• Let automation catch formatting so humans focus on logic.

Frequently asked questions

What should a code review check?

Correctness, tests, security, readability and whether the change fits the design.

How many reviewers are needed?

Usually one; sensitive areas often require two or a code owner.

Can I generate my own review flow?

Yes. Edit the steps in the generator box and press Generate.

Related