Skip to main content

v1.1.1

This release makes it clearer what happens to backups kept in your own storage. A new guide shows how to restore them yourself, and the documentation now explains which backups GitSec encrypts.

Added​

  • Restore from your own storage: A new Restore from Your Own Storage guide shows how to restore a repository's code and history to GitHub, GitLab or Bitbucket from the backup files in your own storage (AWS S3, Azure Blob, Google Drive, Onedrive or Huawei OBS), using Git and your cloud provider's tools, even without access to GitSec. It explains how backup folders are organized, what each scope folder contains and how to push branches and tags to a new repository.

Improvements​

  • Encryption information: A new Encryption section on the Storage Overview page explains how backups are protected. Backups on GitSec Storage are encrypted by GitSec. Your own storage is created and controlled by you, with only the minimum permissions GitSec needs, so backups there are kept as regular files that you can open with your own tools. Pages that described all backups as encrypted have been updated to match.
  • Backup files in your storage: The Storage Overview, Restore Overview and User Settings pages now explain that backup files in your own storage stay accessible in your cloud provider's console, and link to the new restore guide.