Oh no! Did you just accidentally delete that crucial GitHub repository? Try not to panic just yet.
While the initial shock might feel like you’ve lost years of work, there’s a good chance you can recover your lost repository. You just have to know the right steps to follow.
This guide will walk you through restoring a deleted GitHub repository and share some tips to prevent similar incidents in the future.
Why delete GitHub repositories?
Sometimes, developers hit the delete button on GitHub repositories just to keep their workspace tidy. For example, a project might start as two separate repositories but later get combined into one. When that happens, you don’t need both repos anymore, and there’s not much sense keeping the extra one lying around now, is there?
Deleting old repositories can also help avoid confusion. Outdated projects might mislead collaborators or recruiters into thinking they’re active when they’re not. Plus, it’s a great way to reduce security risks—those old repos could contain outdated dependencies or sensitive information you don’t want to leave exposed.
Why would you need to recover a GitHub repository?
Unfortunately, there are times when deleting a GitHub repository isn’t ideal. For instance, you might accidentally delete the wrong repository or delete the right one only to realise, “Oh no, I actually still need that!”
Accidental deletions might be the most common reason for needing to restore a deleted repo, but they’re far from the only one. Malicious actions by employees are another common risk. For example, if you tick off an employee or have to let someone go, they might delete an important repository out of spite. And let’s not forget the possibility of hackers gaining access to your GitHub and altering or deleting code.
You might even revisit an old project you thought you’d never need again—because priorities and circumstances can change quickly. Whatever the reason, if you’ve deleted a GitHub repository and need to get it back, it helps to know if—and how—you can do that.
What is the GitHub data retention policy?
GitHub offers a 90-day grace period for accidental deletions. During these 3 months, you can restore the repository anytime you need. So, if you’ve accidentally deleted a GitHub repo, take a breath, you may still be able to get it back.
But what happens after 90 days? The repository and all its contents are permanently deleted. And unless you’ve set up a GitHub backup solution beforehand, they can’t be recovered.
Guide to restoring GitHub
There are 2 primary methods for restoring your valuable GitHub data. These are:
Method 1: Restore GitHub using GitHub Cloud
To restore a deleted repository using GitHub Cloud, take the following steps. But don’t forget: Only repositories deleted within the last 90 days are recoverable via GitHub Cloud.
- Log in to GitHub: Use the account where the repository was created initially and ensure you have the appropriate permissions
- Go to your repositories: Click your profile picture in the upper-right corner and select Your Repositories. For organisation-owned repositories, visit the organisation’s page first
- Find deleted repositories: Scroll to the bottom of the repositories list. If any repositories can be restored, they’ll appear in a Deleted Repositories section
- Restore the repository: Locate the repository you want to restore, click Restore, and confirm when prompted
- Verify recovery: Check the repository’s contents, test dependencies, and make sure workflows and integrations function correctly
Method 2: Restore GitHub repositories using BackupLABS
GitHub’s built-in recycle bin is handy, but it doesn’t really offer the level of protection your critical code truly deserves. The solution? BackupLABS – a cloud-based backup service that connects directly to GitHub and offers robust data protection.
This paid service offers the following:
- Automatic daily backups (multiple times per day)
- Encrypted storage during transfer and at rest
- Optionally save backups to Google Drive and Dropbox
- Backup and protect repositories, including issues, milestones, commits, branches, labels, comments, Gists, and more
- Detailed audit log
- Easy restoration to GitHub or local device
- ISO 27001/9001 and SOC2 compliance
How to restore a GitHub repository using BackupLABS
If you’re already a BackupLABS customer and have backed up your GitHub data, here’s how to restore it:
- Log in: Sign into your BackupLABS here: https://app.backuplabs.io/auth/login
- Select GitHub: On the left sidebar, under Protected Apps, select GitHub
- Locate the repository: Hover over the repository you want to restore and click View
- Select version: Choose the repository version or date you want to restore, then click Restore
- Complete restoration: Review the details, click Confirm, then select Restore
- Access your restored repository: Your entire repository will appear in your GitHub account within a few seconds and will be renamed with “restored_” at the beginning to avoid confusion
What if your repository cannot be restored?
If your deleted repository doesn’t appear in the GitHub recycle bin, the 90-day grace period has passed, or you’re not a BackupLABs customer, recovery options are limited. But there are still a couple of tricks you can try:
- Check local clones: If you or a collaborator cloned the repository to a local machine, there’s a chance its data was pushed to a new repository.
- GitHub Support requests: If your repo isn’t in the recycle bin but the 90-day retention period hasn’t passed, GitHub Support may still be able to help recover it. Be ready to provide details like the repository’s name, URL, and deletion date.
It’s important to remember that GitHub operates under The Shared Responsibility Model. This means that GitHub keeps its platform secure and functional, but it’s ultimately up to you—and only you—to protect and back up your repositories.
Key takeaway
Deleting a GitHub repository can be a nightmare—but it doesn’t have to stay that way. If you act quickly and follow the steps outlined above, there’s a good chance you can get your vital data back or, at the very least, stop a similar incident from ever happening again.
Using a third-party backup solution like BackupLABS is the safest way to automatically protect your repositories. BackupLABS is compliant with SOC2, ISO 27001, and other industry standards to ensure your data is handled with the highest level of security.
Start your free trial with BackupLABS today and keep your repositories safe, secure, and easily recoverable.
