English
See more
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
0 ★
Manifest Version
2
Web Store Status
Extension ID
Languages Support
Permissions
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
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.
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
