𝐒𝐭𝐚𝐠𝐞𝐬 𝐨𝐟 𝐆𝐢𝐭/𝐖𝐨𝐫𝐤𝐟𝐥𝐨𝐰

Git uses three-tier architecture refers to the three primary areas or stages that files go through in the version control workflow. These stages are the Working Directory, the Staging Area (also known as the Index), and the Repository. Here’s an overview of each stage:

• 𝐖𝐨𝐫𝐤𝐢𝐧𝐠 𝐃𝐢𝐫𝐞𝐜𝐭𝐨𝐫𝐲

The working directory is the local file system where developers create, edit, and organize their project files. It represents the current state of the project. When you start working on a project, your files exist in the working directory.

• 𝐒𝐭𝐚𝐠𝐢𝐧𝐠 𝐀𝐫𝐞𝐚 (𝐈𝐧𝐝𝐞𝐱)
The staging area is an intermediate area between your working directory and the Git repository. It allows you to selectively choose which changes you want to include in your next commit. In other words, it acts as a buffer where you can review and organize your changes before making them part of the permanent Git history.

To move changes from the working directory to the staging area, you use the 𝐠𝐢𝐭 𝐚𝐝𝐝 command. This command allows you to specify which files or changes you want to include in the next commit.

Once changes are added to the staging area, they are considered “staged” and are ready to be committed.

• 𝐋𝐨𝐜𝐚𝐥 𝐑𝐞𝐩𝐨𝐬𝐢𝐭𝐨𝐫𝐲

The local repository is where Git permanently stores your committed changes. It contains a complete copy of the project history, including all branches and commits. Each developer working on a project has their own local repository.

To commit changes from the staging area to the local repository, you use the 𝐠𝐢𝐭 𝐜𝐨𝐦𝐦𝐢𝐭 command. A commit includes a unique identifier (SHA-1 hash), the author’s details, a timestamp, and a commit message describing the changes.

Commits become part of the Git repository’s history, and the HEAD points to the latest commit. The repository contains the complete history of your project, and each commit represents a specific state of the codebase.

𝐆𝐢𝐭 𝐖𝐨𝐫𝐤𝐟𝐥𝐨𝐰 𝐎𝐯𝐞𝐫𝐯𝐢𝐞𝐰:

• 𝐖𝐨𝐫𝐤𝐢𝐧𝐠 𝐨𝐧 𝐅𝐢𝐥𝐞𝐬: Developers start by working on their project files in the working directory. They create, edit, and organize files as needed.

• 𝐒𝐭𝐚𝐠𝐢𝐧𝐠 𝐂𝐡𝐚𝐧𝐠𝐞𝐬: Developers use the 𝐠𝐢𝐭 𝐚𝐝𝐝command to move specific changes or files from the working directory to the staging area. This allows for selective inclusion of changes in the next commit.

• 𝐂𝐨𝐦𝐦𝐢𝐭𝐭𝐢𝐧𝐠 𝐂𝐡𝐚𝐧𝐠𝐞𝐬: After staging changes, developers use the 𝐠𝐢𝐭 𝐜𝐨𝐦𝐦𝐢𝐭command to create a snapshot of the changes in the staging area. Commits include a commit message that describes the changes made. The committed changes become a part of the Git repository’s history.