Skip to Content
Gitza is pre-launch. Join the waitlist and we’ll email you the moment you can create your account.
Exporting and leaving

Exporting and leaving

The whole pitch is that you are in control of where your code lives, and that includes the freedom to take it with you. Nothing on Gitza is designed to make leaving hard.

Your code

A Git repository is already a full copy of itself. On any machine:

git clone --mirror git@git.gitza.co.za:you/your-repo.git

--mirror fetches every branch, every tag and every ref, not only the ones you had checked out. Push that to any other Git host and the history is identical, byte for byte.

Issues, pull requests and the rest

Gitza’s migration tooling is part of its open-source foundation, and other forges built on the same foundation can migrate from Gitza the way Gitza migrates from GitHub: point them at the repository with a Gitza access token that has read access, and they pull the issues, pull requests, labels, milestones, releases and wiki.

The Team tier includes organisation-wide export.

Deleting

  • A repository: its Settings → Danger Zone → Delete This Repository. Gone, along with its issues, pull requests and wiki.
  • An organisation: Settings → Delete Organisation, after its repositories are deleted or transferred.
  • Your account: Settings → Account → Delete Account. Repositories you own go with it; transfer any you want to survive first.

Deletion is immediate in the interface. Deleted data leaves the backups as those are rotated; the backups live in South Africa like everything else.

On Enterprise

Your operator agreement covers return and deletion of your data on exit, in writing. Ask for the export and we do it.

CI/CDSupport