The quick-start guide to Back up submodules — Before winter

If you have tried Back Up Submodules before and bounced off, the problem is usually ordering, not difficulty. Follow the steps in sequence and verify each one.

What you need

• Command-line access
• Your config backup location
• A test environment or spare machine

Step by step

1. Handle the common failure: if the verification fails, roll back and re-check the previous step rather than piling on changes.
2. Apply the smallest change that moves you toward the goal — one setting, one file, one command.
3. Document what you changed and why, so future-you can undo it in minutes.
4. Prepare the environment: update packages and confirm you have the required permissions before touching configuration.
5. Schedule a review: revisit the setup after a week and prune anything unused.
6. Verify the change took effect with the relevant status or version command before continuing.

Tips

• Set a timer; scope grows to fill available time.
• Keep a 'problems' list while working instead of fixing mid-flow.
• The second rep is always faster — plan for it.

Common mistakes

• Starting without checking you can undo the change.
• Ignoring small warning signs because the job technically works.
• Buying gear before earning the skill that uses it.

FAQ

Can I adapt this to my situation?

Yes — treat the steps as the skeleton. Keep the verification steps; customize everything else.

Do I need special equipment?

No. The lists above stick to essentials. Upgrade only after the basic version works and you know which limitation actually bothers you.

How do I maintain the result?

Add the final maintenance step to a calendar. Ten minutes monthly prevents most regressions.

Related guides

[[how-to-set-up-a-commit-signing-setup]] [[how-to-set-up-large-files-with-lfs]] [[how-to-set-up-patch-series]] [[how-to-set-up-worktrees]]

Bookmark this guide and run it as a checklist next time — speed comes from the third repetition onward.