GitHub backup coverage

GitHubBy

To enable GitHub backup and restore functionality, we use the Git Native Protocol (GNP), which facilitates direct and efficient transfer of repository data, including commits, branches, and objects, between client and server, bypassing the overhead of HTTP.

The table below shows the detailed backup and restore coverage of the latest version of Keepit for GitHub.

Knowledge base GitHub

Functional uses	Element	Backup Supported	Restore Supported	Comments
Git Repository
Stores and tracks all code changes over time with complete version history	Blobs and Trees	✅	Via GNP
	References	✅	Via GNP
	Branches	✅	Via GNP
	Commits	✅	Via GNP
	Tags	✅	Via GNP
	Git LFS Objects	❌	❌
Users
	User	✅	❌	API limitations
	Teams	✅	✅
Repositories & Config
Controls who can access repositories and how they behave	Wiki Repository	❌	❌
	Repository Settings	✅	✅
	Repository Collaborators	✅	✅
	Repository Contributors	✅	✅
	Topics	❌	❌
Collaboration & Docs
Enables team communication, code review, and project documentation	Issues	✅	✅
	Issue Comments	❌	❌	Future iterations
	Pull Requests	✅	✅
	Pull Requests Comments	✅	✅
	Milestones	❌	❌	Future iterations
	Labels	✅	✅
	Gists	❌	❌
	Sub-issues	✅	✅
	Issue Types	✅	✅
	Discussions	❌	❌
CI/CD & Automation
Automates testing, building, and deployment of code changes	Webhooks	❌	❌
	Pipelines	❌	❌
	Deployment Keys	❌	❌	Future iterations
	Actions Secrets	❌	❌	Future iterations
	Environments	❌	❌	Future iterations
Releases
Manages software version distribution	Releases	❌	❌	Future iterations
Manages software version distribution	Release Assets	❌	❌	Future iterations

GitHubBy

Coverage details

For a list of coverage details, please download this document.

Knowledge base GitHub

GitHub Documentation

GitHub backup coverage

GitHub backup coverage

Coverage details

Related articles

Create a GitHub connector

Find data for recovery