Brings better blame traversal links to github's blame and commit pages.

Latest Version

Version
1.1.0
Update
May 22, 2015
Size
49.67KiB
Developer
Category
Users
37
Rating
1 ★
Manifest Version
2
Web Store Status
Languages Support
English
See more
Permissions
See more

Github Blame Tool Extension

Github is a great tool, but it could use a few better links to blame views.

On a blame page, beside every short commit hash, you'll see a < and a |, which link to a blame of that file from the commit before that hash and that hash, respectively.

On a commit blob page, every file now also has a button linking to a \"Previous Blame\" view and a \"Blame\" view, that open that file up in blame mode either at the commit previous to the blob you're examining, or at the current commit.

Sometimes, an edit to a file will have been made at a commit prior to a rename of that file. If you're looking at a blame of the file after it's been renamed, you won't be able to jump straight to the blame of the file before it was renamed. You will instead have to follow the commit link for that change, and then on the commit page (which will show the original file), navigate to a blame on _that_ file.

If you have any questions or comments, feel free to contact me at [email protected].

Also, if this somehow breaks something for you, you're the only one responsible for it.
Read more

Source Manifest.json

{"update_url": "https://clients2.google.com/service/update2/crx", "manifest_version": 2, "version": "1.1.0", "content_scripts": [ { "matches": ["https://github.com/*/blame/*"], "js": [ "jquery-1.11.3.min.js", "blame-tool.js", "github.js" ], "css": ["blame-tool.css"] }, { "matches": ["https://github.com/*/commit/*"], "js": [ "jquery-1.11.3.min.js", "commit-blame-tool.js", "github-commit.js" ] } ], "name": "Github Blame Tool", "description": "Brings better blame traversal links to github's blame and commit pages.", "icons": { "16": "icon16.ico", "32": "icon32.ico", "64": "icon64.ico" }}
Read more

How to download and manually install Github Blame Tool extension for Chrome

Looking for a way to install Github Blame Tool extensions for Chrome, you can search for them in the Chrome Web Store, clicking the "Add to Chrome" button, and following the straightforward process.

However, you may need to install Github Blame Tool extensions manually, this article outlines two simple methods to effortlessly install Github Blame Tool extensions, whether they come as unpacked folders in compressed formats like .zip or as .crx files.

Method 1: Download Github Blame Tool extension and manually install through Drag &Drop

If you ever need to manually install a Github Blame Tool extension for Chrome, don't worry, it's a simple process. Just follow these easy steps, and you will have your extension ready to use in no time.

Step 1: Download the Github Blame Tool Extension by clicking the "Download CRX" button on the website.

Look for the Github Blame Tool extension you wish to install. Go to the website and download the Github Blame Tool extension package, which is usually a .CRX file and comes in a zipped file. Here ".crx" file is the format for Github Blame Tool extension that contains all the data.

Step 2: Extract &Arrange Files

Once the file is downloaded, extract that file into its own folder. Similarly, give that extension files a permanent home. In other words, keep it in a folder that you don't accidentally delete it because these files will be needed to make that extension work.

Step 3: Go to the Chrome Extensions Page

Open Google Chrome and in the address bar, type chrome://extensions; it will open the Google Chrome extensions page. Make sure that "My extensions" is selected in the sidebar.

Step 4: Drag and Drop the Extension

Now, go to the folder where you extracted the Github Blame Tool extension and drag &drop the extension file from there anywhere onto the extension page within Google Chrome.

Step 5: Complete the Installation

Once you drag and drop the extension file, follow the steps that Google Chrome takes you through. Similarly, if the extension file is of .crx file format, you will be required to review the permissions and then add the extension.

Now, you can manage that added extension as you would like to with any other Chrome extension that you added through Chrome Webstore. Its icon will also appear in the Google Chrome Menu on the right side of the address bar once you activate it.

Method 2: Download Github Blame Tool extension for Chrome and install in Developer Mode

This is another method to install Github Blame Tool extension manually, but the twist is that here, you install by enabling the developer mode option provided in Google Chrome. This mode is commonly used for testing extensions or running unpublished tools.

Step 1: Download the Github Blame Tool extension file

Select and download the Github Blame Tool extension by clicking the 'Download CRX' button on the website.

Step 2: Extract the downloaded contents

Convert the file to a ZIP file if it is in CRX format then extract the Github Blame Tool extension zip file or folder that you downloaded. Make sure you extract it using the same folder name and keep it safely in another folder, so you don't delete it by mistake. The extracted folder will be needed to keep your Github Blame Tool extension running.

Step 3: Open Chrome Extension Setting Page

In the address bar of Google Chrome, type chrome://extensions and open the Chrome Extension Page.

Step 4: Enable Developer Mode

After opening the Chrome Extension page, look at the top right side, and you will find the toggle option of "Developer mode."Simply enable that developer mode option.

Step 5: Load the Unpacked Extension

Once you enable the developer mode option, you will see the menu of Load Unpacked, Pack Extensions and Update. From that, select the option "Load unpacked."

Step 6: Select the Extension Folder

Once the pop-up opens upon clicking Load unpacked, select the Github Blame Tool extension directory and click on the "Select Folder "button.

Step 7: Confirm and Install

After you select an extension folder of a Google Chrome extension you're installing manually, confirm its installation for the final time and let the installation complete.

Conclusion

Here we've made a step-by-step guide on How to manually install Github Blame Tool extension in 2 ways. We hope this guide proves helpful.

Similar Extensions

icon

GitHub Enhancement Suite Extension · Developer Tools 37 1 ★ 56.24KiB

icon

Clutter Free - Prevent duplicate tabs Extension · Productivity 37 203 ★ 411KiB

icon

Enhanced GitHub Extension · Developer Tools 37 59 ★ 47.01KiB

icon

GitHub Monitor Extension · Developer Tools 37 0 ★ 36.81KiB

icon

GithubPulse Extension · Productivity 37 2 ★ 524KiB

icon

v2ex plus Extension · Productivity 37 102 ★ 64.7KiB

icon

Octotree - GitHub code tree Extension · Developer Tools 37 1139 ★ 3.54MiB

icon

GitLab Approvals Extension · Developer Tools 37 1 ★ 340KiB

icon

github.monkeypatch.pullrequests Extension · Developer Tools 37 0 ★ 1.27MiB

icon

GitHub Hovercard Extension · Developer Tools 37 41 ★ 121KiB

icon

Pretty Pull Requests (Github) Extension · Developer Tools 37 21 ★ 412KiB

icon

GitHub Isometric Contributions Extension · Developer Tools 37 102 ★ 101KiB

icon

Sourcegraph Extension · Developer Tools 37 169 ★ 8.22MiB

icon

OctoLinker Extension · Developer Tools 37 110 ★ 184KiB

icon

Refined GitHub Extension · Developer Tools 37 213 ★ 572KiB

icon

GitHub News Feed Extension · Accessibility 37 2 ★ 175KiB

icon

GitHub Repository Size Extension · Developer Tools 37 80 ★ 12.9KiB

icon

GitHub markdown ToC Extension · Productivity 37 1 ★ 45.48KiB

icon

豆瓣电影传送门 Extension · Productivity 37 2 ★ 14.2KiB

icon

Notifier for GitHub Extension · Developer Tools 37 54 ★ 75.23KiB

icon

GitHub - LGTM Extension · Developer Tools 37 2 ★ 25.72KiB

icon

Github Fork Confirmation Extension · Developer Tools 37 1 ★ 17.08KiB

icon

DevTools Author Extension · Developer Tools 37 117 ★ 377KiB

icon

Github Gist logo fixer Extension · Developer Tools 37 1 ★ 4.12KiB