linkVisual demo of pull request code review compared to GitHub
GitClear's pull request review constitutes a substantive upgrade compared to the classic Myers Diff-based PR diffs offered by tools like GitHub, GitLab and Bitbucket.
Given the sheer volume of substantive differences, the fastest way to understand what GitClear pull request code review offers is probably to skim the video that we made to demonstrate how it works:
Click the image (or here) to visit Youtube for a side-by-side demo with GitHub
As described by The New Stack and Stack Overflow, GitClear undertook research on 49 developer participants, measuring their "time to review" and "code comprehension" when comparing randomly assigned pull requests on GitHub and GitClear.
The developer interviews and test scores in the linked research support the notion that showing developers less code allows them to review pull requests more rapidly, with neutral-to-slightly-positive impact on code comprehension.
linkA few representative differences visualized
Reviewing pull request code in the "Code" tab
Compared to other git viewers, the GitClear PR diff viewer has a number of advantages to expedite code review:
Summarization of every file, and every consequential code block. Assuming you have enabled OpenAI code sharing, our code review will include a brief synopsis of how each file changed. If there are individual change blocks in the file that are non-trivial, those too will be available to view as summaries.
More precise operation labeling. GitClear recognizes code operations that standard git viewers can't: Moved code (30% of all changes), Find & Replace code (5%) and Copy/Paste code (hopefully < 1% 🤞). Labeling moved code as such can save a great deal of time vs. reading a block of code marked as "deleted" by a traditional git viewer, that in fact was just moved to a different file.
Indicate relative volume of work per-file. The left file navigator suggests which files received the lion's share of attention during development. Files that are accompanied by a mostly- or fully-filled circle are files that had the greatest amount of Diff Delta accumulate within them. If you have a limited amount of time to review the pull request, start with the full-circle files.