Github Blame Tool
大小:49.67KiB版本:v 1.1.0更新时间:2021-12-21
Brings better blame traversal links to github's blame and commit pages.
Github Blame Tool 的使用方法详解,最全面的教程
Github Blame Tool 描述:
用户数:36
分类:开发者工具插件
扩展大小:49.67 KiB
最后更新时间:2021-12-21
版本:v 1.1.0
Github Blame Tool 插件简介:
这是来自Chrome商店的 Github Blame Tool 浏览器插件,您可以在当前页面下载它的最新版本安装文件,并安装在Chrome、Edge等浏览器上。
Github Blame Tool插件下载方法/流程:
点击下载按钮,关注“扩展迷Extfans”公众号并获取验证码,在网页弹窗中输入验证码,即可下载最新安装文件。
Github Blame Tool插件安装教程/方法:
(1)将扩展迷上下载的安装包文件(.zip)解压为文件夹,其中类型为“crx”的文件就是接下来需要用到的安装文件
(2) 从设置->更多工具->扩展程序 打开扩展程序页面,或者地址栏输入 Chrome://extensions/ 按下回车打开扩展程序页面
(3) 打开扩展程序页面的“开发者模式”
(4) 将crx文件拖拽到扩展程序页面,
完成安装如有其它安装问题,
请扫描网站底部二维码与客服联系如有疑问请参考:
https://www.extfans.com/installation/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 carss.w@gmail.com.
Also, if this somehow breaks something for you, you're the only one responsible for it.