One command.Every repo safely checkpointed.
MadLabz Repo Backup is a local developer utility for safely checkpointing multiple Git repositories without opening every project one by one.
Choose which repositories to protect, preview every backup, and optionally schedule automatic checkpoints. Repo Backup pushes only to each repository's existing Git remote.
MADLABZ REPO BACKUP v0.6.2 | DASHBOARD
============================================================
[INFO] Run 'repo-backup backup -DryRun' to preview a safe checkpoint.
Multi-repo by default
See the state of all protected repositories in one concise dashboard.
Blocks instead of guessing
Remote divergence, active Git operations and suspicious secret states stop the checkpoint.
Opt-in automation
Keep repos Manual or choose Hourly, Every 6 hours or Daily schedules independently.
How it works
A Git checkpoint workflow designed to be conservative.
Discover
Scan common development folders and review the Git repositories Repo Backup finds.
Choose
Explicitly select the repositories you want protected. New discoveries stay off by default.
Safety check
Review Git state, remote state, sensitive files, generated directories and changed content.
Checkpoint
Create a timestamped Git checkpoint only when files changed, then push only when the remote is safe.
Safety first
A blocked backup is better than a guessed Git operation.
Repo Backup is intentionally not a conflict resolver. When Git history needs human judgement, it stops and tells you what needs attention.
Install once
Then run it from anywhere.
Download and extract the Windows release ZIP.
Run VALIDATE-PACKAGE.cmd and confirm both checks pass.
Run INSTALL.cmd.
Open a new Git Bash or PowerShell window.
Run repo-backup onboard.
First commands
repo-backup version repo-backup demo repo-backup onboard repo-backup repo-backup backup -DryRun
The demo is read-only. Onboarding does not enable newly found repos until you explicitly select them.
Automatic checkpoints
Schedule the repos that matter. Leave the rest Manual.
01
Manual
02
Hourly
03
Every 6 hours
04
Daily
Windows wakes Repo Backup hourly. Repo Backup decides what is actually due, skips clean repos, waits for the idle window, then runs the same safety checks used by manual backups.
Need help getting started?
Follow the complete setup guide from download to your first protected repo.
A beginner-friendly walkthrough covering installation, onboarding, Dry Run, automatic schedules, repository management, troubleshooting and updates.
FAQ
Straight answers before you give a tool access to your repos.
Does Repo Backup upload my code to MadLabz?
No. Repo Backup runs locally on your Windows machine. When a checkpoint is safe, normal Git pushes it only to the remote already configured for that repository. MadLabz does not receive or store your repository code.
Is this a replacement for Git?
No. Repo Backup is a safety-focused multi-repository checkpoint utility built on top of normal Git repositories, branches, commits and remotes.
What happens if my computer is turned off when a backup is due?
Nothing runs while the computer is off. When Windows is running again, Windows Task Scheduler resumes and Repo Backup checks which repositories are due on its next scheduled run. It checkpoints the current state when appropriate instead of creating a separate catch-up commit for every missed interval.
Do I need to leave Repo Backup or a terminal open?
No. Once automatic scheduling is configured, Windows Task Scheduler launches Repo Backup for you. Git Bash, PowerShell and the Repo Backup dashboard do not need to stay open.
What if I'm actively coding when an automatic backup is due?
Automatic mode waits for an idle window rather than blindly checkpointing in the middle of active edits. When the repository is ready, it runs the same safety checks used by manual backups.
Will it create commits every hour?
No. The scheduler may wake Repo Backup hourly, but clean repositories are skipped. Each repository also follows its own Manual, Hourly, Every 6 hours or Daily cadence.
What happens if a branch has changed remotely?
Repo Backup fetches first and blocks instead of guessing when the remote is ahead or history has diverged. It does not automatically pull, merge, rebase or resolve conflicts.
Does Repo Backup change branches or rewrite my Git history?
No. Repo Backup does not switch branches, rebase, force-push, auto-merge or resolve conflicts. It works conservatively with the repository and branch you already have checked out.
What happens if one repository has a problem?
Repositories are evaluated independently. The affected repository can be blocked and marked for attention without Repo Backup trying to perform risky Git operations to fix it. Resolve that repository normally, then retry it.
Can I turn automatic backups off for one project without removing it?
Yes. Set that repository to Manual. Other repositories can remain on Hourly, Every 6 hours or Daily schedules.
How do I stop all automatic backups or remove Repo Backup?
To stop one project, set it to Manual. To stop all unattended runs, use repo-backup schedule remove to remove the Windows Task Scheduler trigger. The complete setup guide also explains full removal. Removing Repo Backup does not delete your Git repositories.
What if VALIDATE-PACKAGE.cmd does not pass?
Do not install the package. Download the latest Windows release ZIP again, extract it and rerun validation. If either check still fails, do not bypass the validator; report the exact output so the package can be investigated.
Can I get my files back from a Repo Backup checkpoint?
Repo Backup creates normal Git checkpoint commits rather than a proprietary backup format. Your checkpoint remains part of ordinary Git history, so recovery uses normal Git tools and workflows.
Is it free?
Yes. Repo Backup is free and open source under the MIT License.
Does it work on macOS or Linux?
The current public beta is Windows-first. The core model is portable, but the v0.6 installer and unattended scheduler use Windows tooling.