When working on a product with multiple independent repositories, it is common to have separate repositories for the backend, frontend, mobile application, smart contracts, admin panel, or shared services.

For example:

Product Master Repository
│
├── backend
├── frontend
├── mobile
├── contracts
└── admin

One approach is to combine everything into a monorepo. Another approach is to keep each project as an independent repository and use Git submodules to bring them together under a master repository.

Git submodules are useful when you want to maintain repository independence while still having a single place that represents the complete product.

This article explains how Git submodules work, how to manage branches, how to update repositories, and the commands I use most often.

The only Git guide you need for 95% of your daily development workflow. Save this post or bookmark it — it’s your quick-fix toolkit for everyday Git challenges.

Why This Guide​

Git can feel complicated when you are managing multiple branches, commits, and conflicts. Whether you are a developer, team lead, or project manager, this post walks through real-world Git scenarios and commands that actually work, not just theory.

Writing meaningful commit messages is crucial for maintaining a clean and understandable Git history. The Conventional Commits specification provides a structured way to write commit messages, making it easier to automate versioning, track changes, and collaborate effectively.

This guide covers all standard commit types, explaining their use cases and best practices.

Managing dependencies and shared codebases across multiple projects can be a challenge in software development. Git submodules offer a powerful solution by allowing you to embed one Git repository as a subdirectory within another. This article explores what Git submodules are, why they are useful, and how to work with them effectively through a step-by-step guide.

Git for Absolute Beginners: A Comprehensive Guide with Clear Examples

Git is a powerful version control system that allows multiple people to work on a project simultaneously, keeps track of changes, and facilitates collaboration. If you're new to Git, don't worry! This guide will walk you through the basics with clear, step-by-step examples.

What is Git?​

Git is a distributed version control system designed to handle everything from small to very large projects with speed and efficiency. It allows you to:

• Track changes in your code
• Revert to previous versions
• Collaborate with others