See below which features MergeBoard supports and how they can simplify your everyday life as a developer. The table reflects the status as of June 2021.

Diff Visualization

Unified Diff
Hide Style Changes
Hides changes that do not affect the program flow, like adding line breaks between function parameters.
Grouping of Changes
Visualizes repeated changes by assigning them the same color.
Highlight Moved Code
Indicates how a block of code has been moved and whether it contains modifications.
Minimap of Diff


Change Requests
Comments that need to be addressed before a merge request can be merged.
General Comments
Reference Arbitrary Lines
Reference multiple lines of code from a comment / change request.
(even across files)
Shown Across Commits/Revisions
Comments are shown at the correct position in the code after a rebase and across commits.
Switching Between Code Revisions
Switch between revisions in the comment overview to see how the referenced code has changed.
Fixed and Resolved State
Change requests can be marked as fixed without resolving them.


Mark Lines As Reviewed
Reviewed Lines Are Kept Across Rebases
Lines keep their review marker unless a new revisions modifies them.
Require Approvals
A configurable number of reviewers must approve a merge request before it can be merged.
Require CI To Pass
Scanner Annotations As Change Requests
Scanners create change requests that need to be fixed or marked as false positive / intentional.
(in MergeBoard integrated scanners)
Compare Revisions
Compare different revisions of a merge request against each other.
Automatic Time Tracking
Automatically aggregates the time the author and reviewers spend on a merge request.


Git Repository Hosting
(acts as git client)
Merge Branches
Allows merging from/into any git remote reachable via SSH or HTTP(S).
Integration of External CI
The state of the external CI influences whether a merge request can be merged.
(GitLab, GitHub, Bitbucket)


Own Login System
Users can register an account, change their password, etc.
OAuth Login
Users can login using a third-party OAuth account.
(GitLab [1], GitHub [1], Google)
Groups can be part of other groups.
  1. Both SaaS and self-hosted versions are supported.