Uploaded image for project: 'Bitbucket Cloud'
  1. Bitbucket Cloud
  2. BCLOUD-4693

History for a File does not follow renames

    XMLWordPrintable

    Details

    • Feedback Policy:

      Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Description

      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)

        Attachments

          Activity

            People

            Assignee:
            Unassigned
            Reporter:
            b447fde8ed68 Rob Vesse
            Votes:
            5 Vote for this issue
            Watchers:
            4 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: