1. Bitbucket Website
  2. Public Issue Tracker
  3. master

Issues

Issue #4693 duplicate

History for a File does not follow renames

Rob Vesse
created an issue

I recently did a source re-organisation on one of my projects using hg rename

This means that when I now view the file online there is no history prior to the rename shown in the BitBucket interface. I am aware that the hg command line client requires the --follow argument to follow renames so it appears that BitBucket does not utilize this (or the programmatic equivalent)

Even if this is not enabled by default for projects it would be useful to be able to enable it on a per-project basis. Also it would be useful to allow users to enable this on a per-file basis when browsing the source (possibly even include a per-user preference on whether they want to always follow renames)

Comments (4)

  1. Log in to comment