Source code
Find and export
your Bitbucket data.
Bitbucket repository storage measures code and Git history. Pull requests, comments and legacy issue data need separate coverage when describing the broader development record.
- Report in
- GB
- Category
- Source code
- Last checked
Find your Bitbucket data size
- Open each repository with the required administrator or read access.
- Review Repository settings → Repository details → Size where available.
- For a measured copy, create a mirror clone and inspect its folder size or git count-objects -vH output.
- Add non-overlapping repositories and any LFS material, identifying the units used.
What to include in your data inventory
Report in GB, with repository count and code-history scope. Describe LFS, pull requests and any retained issue archives separately.
Give the oldest relevant commits and staff scope, including imported history.
Export your Bitbucket history
- Have a developer create git clone --mirror REPOSITORY_URL archives for the agreed repositories.
- Fetch required LFS objects separately.
- Review supported API or existing archive routes for pull requests and comments.
- Check where any former Bitbucket issue-tracker history was exported or migrated, such as Jira.
A mirror clone preserves Git branches, tags and history. Collaboration records stored by the hosting service need separate extraction.
Bitbucket's issue-tracker availability has changed. Confirm the location of any legacy business history rather than assuming it is still in the repository interface.
Why Bitbucket data has value for AI training
Code history can show how a team changes and maintains an application.
Related review discussions and issues can supply the reasoning and requirements behind the changes.
What stays private
Choose repositories and collaboration records in scope, reviewing proprietary code and sensitive discussion content.
Telegraph Lab reviews the proposed material with you and agrees how sensitive information will be handled. Preparation can include excluding material, redacting details and replacing personal identifiers. Your company keeps ownership; the licensing agreement defines the material, permitted uses and authorized recipients.
Common questions about Bitbucket data
Can a source ZIP represent the entire history?
Use a mirror clone when all branches and retained commits are required.
Are pull requests in a Git clone?
They are separate hosting-service records. Plan an additional collection.
Where might old issue-tracker data be?
Check prior exports and migrations with the account administrator, including any Jira destination.
Should LFS be counted?
Include it when those large files form part of the agreed dataset, identifying their size separately.