Bitbucket commits full history does not appear after migration to cloud
Platform Notice: Cloud Only - This article only applies to Atlassian products on the cloud platform.
Summary
After migrating from the Data Center to Bitbucket Cloud, the commit history shown is different from the Data Center.
On-prem shows the entire commit history. All the commits exist in the cloud but don't appear in the commit history view.
Environment
Bitbucket Cloud
Diagnosis
It is possible to diagnose if the file was renamed by the following comparison on both environments.
Open the required file in Bitbucket Cloud and Bitbucket server:
In the Bitbucket Data Center, open the History tab
bitbucket.instanceName.com/projects/ProjectName/repos/Repository/browse/File
In the Bitbucket Cloud open the commit tab
If the Bitbucket Datacenter contains more commits in the history tab than Bitbucket Cloud, it means that the file was indeed renamed, and hence, Bitbucket Cloud won't show the same data.
Cause
Bitbucket server considers file renaming, while Bitbucket cloud does not follow this logic.
In this case, the Bitbucket cloud does not show the list of the commits in the history if the file name has been modified.
Solution
For Bitbucket Cloud repositories, it's possible to view the entire file history locally, including renames, by using the flags below on the git log command:
1
git log --follow -- filenameA feature request has also been raised to follow file renames through history in Bitbucket cloud.
If this feature is affecting your workflow, please vote and leave your comments at the following link:
Was this helpful?