How the PR Tool was built to speed up the review process

More efficient code reviewing with my PR Tool

Every developer knows the problem: you submit a merge request, and it takes forever to get feedback. This leads to delays, extra work, and sometimes even frustrating conflict situations. That had to change, I thought. And so, I built the PR Tool.

Why the PR Tool?

The review process is a crucial part of software development, but it can also be a bottleneck. Waiting too long for feedback means your work gets stalled, and accumulated changes can result in complex merge conflicts.

I frequently encountered this problem myself. I decided to build a solution that my colleagues and I could use to speed up the review process: a desktop application that provides instant insight into which pull requests need attention.

How does the PR Tool work?

The PR Tool is designed to help developers work faster and more efficiently. The main features include:

• Instant overview: The tool displays, at a glance, which merge requests or pull requests are waiting for review.
• Faster feedback: By offering a clear priority list, team members can quickly switch gears and review each other's work.
• Minimalist interface: No unnecessary distractions, just the information you need.
• Integration with GitLab: Recently, I released an update that allows the tool to seamlessly work within th[is]'s GitLab setup.

How did I build it?

This project started as a personal initiative. I worked on it during weekends, aiming to develop a practical and efficient solution. I chose Electron and Svelte as core technologies because that way I could develop an application with web technology that works on all desktop platforms.

Of course, there were challenges along the way. As I like to say: "How did I overcome technical obstacles? Pure willpower 😄".

What are the benefits?

With the PR Tool, it's easier than ever to gain insight into outstanding pull requests. No more long waiting times, no endless Slack messages asking for reviews—just a clear dashboard showing what needs priority. This means less frustration, faster releases, and fewer merge conflicts.

What's Next?

I’m proud of what I’ve accomplished and have plans to expand the tool further. One of the next features I want to add is Jira support, so the tool better integrates into existing workflows.

The review process doesn’t have to be a bottleneck. With the right tools and determination, it can become a smooth and streamlined part of software development!

Want to check out the PR Tool for yourself? Visit: https://bfanger.nl/projects/pr-tool

Bob

Frontend Developer