Github Turbo PR

An extension to optimize github for handling big pull request. 🚀

Github Turbo PR - Optimize Github for big pull requests

Github Turbo PR is a Chrome extension that optimizes Github pull request pages for handling large PRs. It makes the page more responsive by detaching file diffs that are not visible and reattaching them when they are needed. This improves performance and allows reviewers to spend less time reviewing code and more time enjoying a refreshing drink.

Download

Extension stats

By: sudhanshuyadav2

Users: 76

Version: 0.2.1 (Last updated: 2018-04-09)

Creation date: 2018-04-08

Risk impact: High risk impact

Risk likelihood:

Low risk likelihood

Manifest version: 2

Permissions:

https://github.com/*
webNavigation

Size: 38.52K

Ranking

# 74,535 ▲ 750

Other rankings

#16851 in Workflow & Planning ▲ 188 #203 in optimize keyword 66 ▼ 2 #217 in pull keyword 92 ▲ 3

Other platforms

Not available on Android

Not available on Firefox

Not available on Edge

Want to check extension ranking and stats more quickly for other Chrome extensions? Install Chrome-Stats extension to view Chrome-Stats data as you browse the Chrome Web Store.

Extension summary

Analyze keywords

Github pull request page gets unresponsive on a big PR and makes it very hard to review. This extension optimize the page to make it more responsive so that you spend less time reviewing code and more time drinking beer 🍻.

Usage

For non Pull Request page the extension will be inactive. On a PR compare page it will get active but by default it will be disabled. If you feel your page is getting slow on a big PR you can click and enable it. You can toggle it back if you want.

How does it optimize?

It applies a simple trick by detaching file diffs which are not visible and reattach them when they are about to come on viewport. Less DOM nodes in a DOM Tree, more performant the page it. And it does it performantly using Intersection Observer API https://developer.mozilla.org/en-US/docs/Web/API/Intersection_Observer_API.

Known caveats.

As for optimization it detaches file diff from the page, browser find will not work as expected. Though you can search with a file name but not the content.
Count in Review changes gets incorrect, but actually it does not affect any review comments. So don't get scared if number shows wrong.