Code Fixes:9M+ Fixes Applied

Which Developer are You?

Feel More Confident about the Code You Produce

Mauro Morales, Developer

We don’t do any pair programming because most of the time everyone is working on their own code. PullReview helps us to create a standard so that at least when you see someone else's code it still feels like home. It ensures there's a quality standard so that code remains readable and is transferable when necessary by putting more emphasis on testing and the documentation. When we have to collaborate and touch the same source files Fixing or improving code.

It makes me feel more secure about the quality of what I’m pushing to production and I feel more confident when sharing what I’ve worked on.

Ensure Your Team Gets Feedback

Benjamin Roth, CTO

I'm no longer the only bad guy :-). It's important that my development team gets frequent feedback on how to improve their code. What I really like is that developers automatically get notified whenever somebody reinvents something that is already coded elsewhere.

Also extremely useful are the security warnings. Pullreview detects all kinds of security threats sql injections or HTML parameters that can be abused. This tool gives me bang for my buck.

Convince Clients that They Get Quality Code

Mike Rogers, RoR Freelancer

I want to give clients metrics such that they can gauge the quality of code I am producing over a long period of time. PullReview helps me to identify & track these metrics easily. It's very anal about things, this keeps me on my feet. I really like it.

Make Peer Reviewing more Efficient

Kévin Disneur, Lead Developer

We practice peer code reviewing on a daily basis but this is a time-consuming process. Before we ask our colleague for a review we first let it be reviewed by Pullreview so that we can already do a first iteration of fixes. This makes the subsequent review by our colleague much more time efficient because the code is already fixed for the most part.

What I particularly like about Pullreview is that it reviews only the changes you made to the code and not the entire project. When I do a new feature I don't want to be reminded there are lot of problems on the project (I already know), I want to focus on the code I've changed/added.

Get your Branch reviewed, Spot the Problems and Learn How to Fix Them

Get better, review after review.

Improving your coding skills is a balance between learning
and applying what you learned. With PullReview you can
learn while working on your projects and your codebase.

Get feedback on your last commit.

Code reviews are indispensable, but not for all of your code at the same time. PullReview draws your attention to the problems at hand, so you can discuss the bigger project challenges with your peers. Your project gets better with every code review and so do you.

What does a Code Review Look Like?

We can detect 500+ Types of Issues

We are constantly on the lookout for new insights in what
makes better Ruby and Rails code. We sift through
thousands of blog posts, talks, seminars, etc. and add
validated insights to PullReview such that you can produce
better code.

From style to security

PullReview gives you feedback on all aspects of your code:

style (respect of the used conventions)

duplication (we all love DRY)

complexity (better to refactor it now)

the way you document your code (you'll thank
yourself in some months)

typical code smells (so they don't blow off later)

security (to sleep better at night)

Test Driven Development best practices for writing tests for that new feature you've added.

All under the same umbrella, at your fingertips.

Issues are highlighted right within your code

PullReview highlights the code snippet where the issue you
are looking at is located. Like this you can immediately dive
into the right part of the code.

Get insights how to fix the issue

We not only report what's wrong with your code we also
explain why it's wrong and explain different strategies how
you can fix your code.

Best Practices by Ruby Experts

PullReview advocates best practices in its code reviews that are based on the learnings from some of the best ruby developers in the community

Martin Fowler

Martin Fowler is specialized in object-oriented analysis and design, UML and patterns. He's the author of several books that have a profound impact on design practices in the Object-oriented Programming paradigm.

Bozhidar Batsov

Bozhidar is the founder of the Ruby style guide, a community-driven initiative to create a Ruby coding style and best practices.

Sandi Metz

Sandi is the author of Practical Object-Oriented Design in Ruby. She advocates simple code and introduced four metrics that are heuristics for detecting issues with the code.

Getting Started is Easy

Step 1. Connect PullReview to your Git Repository

We support GitHub, BitBucket and GitLab out of the box.
Connecting it is as easy as logging into the services. After
that you just select the repository and branch and you're
ready for your first code review.

Step 2. Push your Work to Your Git Repository

PullReview instantly reviews your changes on the fly. You
get a review per commit that can be ordered by type (e.g.
security issues, coding style, etc) or by severity. Like this
you can focus on fixing the type of issues that matter most
to you.

Step 3. You're Done Already. You can Start to Improve Your Code.

Now that you have feedback you can start improving the
code by fixing reported issues. After you've committed the
fixes PullReview will let you know that they've been fixed.