A practical, step-by-step approach
Step 1
Know what a Git checkpoint protects
Commits capture tracked project history; pushes can copy that history to a configured remote. A Git push is not a full machine or file-system backup, and ignored files, untracked content and secrets may not be included.
Try this: Keep a separate backup for databases, uploads, untracked assets and other material outside Git history.
Step 2
Make a clear list of repositories
Identify which folders contain active Git repositories, which remote each one uses and which branches are important. Exclude temporary experiments or sensitive projects until you have reviewed them.
Try this: With MadLabz Repo Backup, run guided onboarding and explicitly select each repository. New discoveries remain disabled until selected.
Step 3
Inspect changes before automating
Check for an in-progress merge, rebase or cherry-pick, and inspect tracked content for sensitive files or obvious secret values. Never assume every changed file is ready to commit.
Try this: Review the status of each repository and run the tool's safety review before creating checkpoints.
Step 4
Check the remote before pushing
A remote branch might be ahead of your local branch or have diverged. Automatically force-pushing or merging in this situation can destroy work or create unexpected changes.
Try this: If the tool reports a remote-ahead or diverged branch, resolve it manually. Do not bypass the safety block.
Step 5
Dry-run, checkpoint and schedule deliberately
Preview the workflow, verify which repositories will be affected, then run the actual checkpoint. If you opt into a schedule, remember scheduled tasks only run when the Windows environment allows them to.
Try this: Run repo-backup backup -DryRun first. After checking the output, use repo-backup backup, and test scheduling separately if enabled.
Important limitation
Repo Backup works with your existing Git repositories and configured remotes; it is not an encrypted cloud-backup service or a replacement for full system backups. It deliberately blocks unsafe Git states rather than auto-merging or force-pushing.
Common questions
How do I back up all my Git repositories at once?
First identify your repositories, decide which ones you actually want included, and verify that every remote and branch is in a safe state. A multi-repository tool can then run a repeatable checkpoint workflow without treating all folders the same.
Does GitHub automatically back up every file on my computer?
No. Only content included in Git history and pushed to a remote is present there. Local-only changes, ignored files, untracked files and material outside your repositories require a separate backup strategy.
Should I automatically git add, commit and push every repository?
Not without safeguards. Automatic bulk commits can capture sensitive material, and pushes should be blocked when branches have diverged or the remote is ahead.
Is MadLabz Repo Backup available on macOS?
The current released utility is for Windows. Check the product page and release notes for platform support before installation.
MadLabz Repo Backup
A free Windows developer utility with explicit repo selection, remote-state and secret checks, Dry Run, safe checkpoints and optional scheduling.
Explore Repo Backup →