Storage

Diversion stores your projects and their histories in the cloud. This is what allows you to access your projects from any device and to collaborate with your team. However, this also means that you need to be aware of how much storage you are using and how it is calculated.

​

For each file

Diversion keeps a history of the files in your repository, one version per commit that includes that file. This means that if you have a file that is 1 MB in size and you have made 10 commits that include that file, it will count as 10 MB of storage usage. If you delete that file, it will still count as 10 MB of storage usage, since the history of that file is still stored in the repository and you can always revert to a previous commit that includes that file, or download it from the history. For the same reason, reverting or rolling back commits, replacing a large file with a smaller one, or adding it to .dvignore will not reduce your storage usage. These actions only change your files’ current state, while the older versions remain in your history and continue to count. Admins can reclaim storage in two ways: set a revision limit to keep only the latest N versions of matching files and prune older ones automatically, or use obliterate to permanently remove specific files and their whole history. Deleting the repository or deleting unmerged branches also reduces storage. New files, or files with changes that are not yet committed, are also counted towards your storage quota, since they are synced to the cloud. These are easier to remove, since you can just reset them from your workspace and they will be removed from the cloud as well, and will no longer count towards your storage.

​

For each repository

For each repository, you can see how much storage you are using on its row in the Remote Repositories tab of the dashboard. This is the total size of all the files in the repository, including all the versions of each file.

​

For each organization

For an organization, all of the repositories assigned to that organization are counted. The storage quota is calculated for the owner of the organization. You can see the organization’s total storage on the org settings Repositories page. If an owner or admin of an organization invites a new member, and that member has repositories that are not assigned to any organization, those repositories will be automatically added to the inviting user’s organization and their storage will be counted towards the storage quota of the organization. Also, if an owner or admin of an organization invites a new collaborator to a repository that is part of an organization, the new collaborator will be added as a member. To avoid either of these, you can create a separate Diversion account to use in the organization. For any help, contact support.

​

FAQs

​

Can I delete repository history to free up storage space?

Yes. Repository admins can permanently remove specific files and their history with obliterate. The command takes one or more path patterns and deletes every version of the matching files across all branches and commits. To keep the latest versions but drop the older ones automatically, set a revision limit instead. It keeps only the latest N versions of matching files and prunes the rest as new commits arrive. Going forward: Use a .dvignore file to exclude specific files or folders from future commits. Note that this will not affect items already committed prior to the change.

​

Why am I receiving system messages about exceeding my storage limit?

If you’re seeing system messages like this: This means your total repository storage exceeds your plan’s storage capacity. To resolve this, you have three options:

1. Delete unused repositories - Remove repositories you no longer need to free up space
2. Upgrade your plan - Purchase additional storage capacity to accommodate your needs
3. Move repositories out of your organization - As the organization’s owner, you can transfer any repository in your organization to another organization. See how to move repositories for instructions
4. Delete unmerged branches - If you have unmerged branches that are no longer needed, deleting them can free up storage