Support `git --follow` to preserve history across renames
When a file is moved or renamed, the GitHub History doesn't show commits from before the move. Git itself supports the `--follow` option to show full history in these cases (and apparently it's much less buggy now then it used to be), but there is no way to achieve this in GitHub. This has [been](http://stackoverflow.com/a/5647721/1431146) [requested](http://stackoverflow.com/a/21508105/1431146) [many](http://stackoverflow.com/questions/5646174/github-follow-history-by-default#comment41387473_21508105) [times](http://stackoverflow.com/q/17213046/1431146), but has yet to be implemented. Current workaround seems to be installing [this Chrome extension](https://chrome.google.com/webstore/detail/github-follow/agalokjhnhheienloigiaoohgmjdpned), but that's insufficient for a large dev team.
Posted by cletusw on Mar 10, 2017, 8:56 PM
Tags
Related issues
- Add 65536 size support for maps
- TypeScript 7.1 Iteration Plan
- nvim-treeconfig: upstream nvim-treesitter
- Add the "action" and "method" attributes to <button>
- [FEATURE] Support multiple Connector accounts (same connector, different accounts) in Claude and Claude Code on the web (claude.ai/code)
- > We were imposed GitHub for so many exercises!
Raise real-world problems, find people facing the same issue, and discuss solutions.4,500 issues0 comments
support (Software)
Add 65536 size support for maps
TypeScript 7.1 Iteration Plan
nvim-treeconfig: upstream nvim-treesitter
Add the "action" and "method" attributes to <button>
[FEATURE] Support multiple Connector accounts (same connector, different accounts) in Claude and Claude Code on the web (claude.ai/code)
> We were imposed GitHub for so many exercises!
Add support for Visual Studio 2026 Integration
Support for Helm v4
Support `git --follow` to preserve history across renames
When a file is moved or renamed, the GitHub History doesn't show commits from before the move. Git itself supports the `--follow` option to show full history in these cases (and apparently it's much less buggy now then it used to be), but there is no way to achieve this in GitHub. This has [been](http://stackoverflow.com/a/5647721/1431146) [requested](http://stackoverflow.com/a/21508105/1431146) [many](http://stackoverflow.com/questions/5646174/github-follow-history-by-default#comment41387473_21508105) [times](http://stackoverflow.com/q/17213046/1431146), but has yet to be implemented. Current workaround seems to be installing [this Chrome extension](https://chrome.google.com/webstore/detail/github-follow/agalokjhnhheienloigiaoohgmjdpned), but that's insufficient for a large dev team.
Comments (0)
No comments yet. Start the discussion.