`deep-blame` doesn't support renamed files
See original GitHub issueFeature: https://github.com/sindresorhus/refined-github/pull/2881
- Visit https://github.com/sindresorhus/refined-github/blame/fad67fb8d8fcf608601c9b8ae1b5f12337cbccce/source/options.html#L1
- Click Deep Blame button
- See 404 page
The file is currently source/options.html
but was renamed twice.
The link we generate should point to the file that existed at the time: extension/options/index.html
The regular blame follows renames, but I’m not sure we (deep-blame
) can.
Issue Analytics
- State:
- Created 3 years ago
- Comments:9 (9 by maintainers)
Top Results From Across the Web
Why git blame does not follow renames? - Stack Overflow
"git blame" follows content movements, and never treats "renames" in any special way, as it is a stupid thing to do to think...
Read more >Consider renaming the "Blame" button to "Inspect" - GitLab.org
In 9.3 (gitlab-ce!10378), we changed the "Blame" button to "Annotate" to promote a blameless culture. This change was reverted mostly based ...
Read more >DevOps git blame doesn't track file rename
When you renamed a file and then see it with Blame "view" on DevOps, it shows that the entire content was modified in...
Read more >Git should rename the blame command - Triplebyte
Git should rename the blame command · In case you don't know git-blame · 'Blame' is a pretty negative word · Blame is...
Read more >Rename file in Amazon Glacier - Server Fault
No, the file name is part of the archive content, therefore you can't update it.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hmm, That would not work if the PR had more than 100 files No?
Yes but you would have the same issue if more than 100 files were changed For example #2925