code-review
Mailing list style code reviews for github.
prr is a tool that brings mailing list style code reviews to Github PRs. This means offline reviews and inline comments, more or less.
Related contents:
Distributed code review system for Git repos.
By "distributed", we mean that code reviews are stored inside of the repository as git objects. Every developer on your team has their own copy of the review history that they can push or pull. When pulling, updates from the remote repo are automatically merged by the tool.
This design removes the need for any sort of server-side setup. As a result, this tool can work with any git hosting provider, and the only setup required is installing the client on your workstation.
Related contents:
Cut Code Review Time & Bugs in Half. Instantly.
Supercharge your team to ship faster with the most advanced AI code reviews.
Related contents:
It's a bright day for code review!
An extensible and friendly code review tool for projects and companies of all sizes.
Review Board is an open source, web-based code and document review tool built to help companies, open source projects, and other organizations keep their quality high and their bug count low.
Haystack Editor combines the simplicity of a code editor with a canvas UI that makes it easier to understand code at a glance It provides comprehensive code editing, navigation, and understanding support along with lightweight debugging, a rich extensibility model, and lightweight integration with existing tools.
Gerrit is a code review and project management tool for Git based projects.
Gerrit makes reviews easier by showing changes in a side-by-side display, and allowing inline comments to be added by any reviewer.
Gerrit simplifies Git based project maintainership by permitting any authorized user to submit changes to the master Git repository, rather than requiring all approved changes to be merged in by hand by the project maintainer.
Gerrit-style code review for GitLab projects.
The branch-based approach that GitLab merge request uses can slow things down when you really want to create dependent MRs so they can be reviewed in parallel. With great amount of manual effort and carefulness, you can actually achieve that by setting an MR's target branch to the one it's dependent on and making sure before merging any MRs, you change their target branch back to master (or any default main branch in your project).