Cross recovery options

This article describes the cross recovery options in GitHub

Cross recovery options

In general, GitProtect allows you to restore the data between GitHub, GitLab, and Bitbucket. Different vendors give you an opportunity to create different metadata, which is not common to all providers. Due to this fact, during the restore process, you can meet the case, when some metadata may be not available to restore. In this article, you will find the information, on which metadata are allowed to restore between GitHub and other Git providers.

Protected GitHub Resources / Elements / Metadata
MetadataRestore to

Repository

Bitbucket, Bitbucket DC, GitHub, GitHub Enterprise, GitLab

Wiki

Bitbucket, GitHub, GitHub Enterprise, GitLab

Issues

Bitbucket (only Open status), GitHub, GitHub Enterprise, GitLab

Issue Comments

Bitbucket, GitHub, GitHub Enterprise, GitLab

Deployment keys

Bitbucket, GitHub, GitHub Enterprise, GitLab

Pull requests (open)

Bitbucket, Bitbucket DC, GitHub, GitHub Enterprise, GitLab

Pull requests (closed)

GitHub, GitHub Enterprise, GitLab

Pull requests comments

Bitbucket, GitHub, GitHub Enterprise, GitLab

Webhooks

GitHub

Milestones

GitHub, GitHub Enterprise, GitLab

Labels

GitHub, GitHub Enterprise, GitLab

Pipelines

GitHub

Tag

Bitbucket, Bitbucket DC, GitHub, GitHub Enterprise, GitLab

Releases

GitHub, GitHub Enterprise

Collaborants

GitHub

LFS

Bitbucket, Bitbucket DC, GitHub, GitHub Enterprise, GitLab

Commits

Bitbucket, Bitbucket DC, GitHub, GitHub Enterprise, GitLab

Branches

Bitbucket, Bitbucket DC, GitHub, GitHub Enterprise, GitLab

You have to know that closed / merged Pull Requests are recovered as closed issues.

Last updated