What is Git/GitHub & Why do we need it? | Git Tutorials #1

Installing Git + Initial Setup? | Git Tutorials #2

Git: Three Stage Architecture | Git Tutorials #3

Tracking Our first Git Project | Git Tutorials #4

Cloning a Remote Git Repository from GitHub | Git Tutorials #5

Git: File Status Lifecycle | Git Tutorials #6

.gitignore: Ignoring Files in Git | Git Tutorials #7

Git Diff: Showing Changes Between Commits/Staging Area & Working Directory | Git Tutorials #8

Git: Skipping The Staging Area | Git Tutorials #9

Moving and Renaming Files In Git | Git Tutorials #10

Git Log: Viewing & Changing Commits In Git | Git Tutorials #11

Unstaging & Unmodifying Files In Git | Git Tutorials #12

GitHub: Working with Remote Repositories | Git Tutorials #13

Setting Alias In Git | Git Tutorials #14

Git: Creating & Switching Branches In Git | Git Tutorials #15

Branching & Merging a Production Grade Project | Git Tutorials #16

Resolving Merge Conflicts (With Example) | Git Tutorials #17

Git Branching Workflow in Production | Git Tutorials #18

Pushing Git Branches To Remote Repositories | Git Tutorials #19

Hey everyone welcome, We are going to learn about Three-stage architecture of git. So let&rsquo;s get started.&nbsp;&nbsp;
&nbsp;
Let&rsquo;s assume we are working on a project which has an index.html file, a folder named static and engine.js file. Now you have completed this and made it version 1 of this project. Now you want to add more features into it and if anything goes wrong, you could roll back to version 1 which runs perfectly. In this case, you will take a snapshot of the project. Which means you will save a state of this project where it is running without any errors. This process is called &ldquo;Commit&rdquo;. Now you have committed this project as C1 and continued to work. Now You have changed index.html and also the other files, but somehow engine.js file is not working anymore. So, in this case, you will just put index.html file on the second snapshot and pull the other working files from the first snapshot. This is where Three-stage architecture comes.&nbsp;&nbsp;
<h4>We have 3 areas in the Three-stage Architecture:</h4>
<ul>
<li style="font-weight: 400;">
<h5>Working Directory:&nbsp;</h5>
</li>
</ul>
The working directory is the folder in your local computer where the project files and folders are stored.
<ul>
<li style="font-weight: 400;">
<h5>Staging Area:&nbsp;</h5>
</li>
</ul>
The staging area has those files who are supposed to go to the next commit. Only those files which are needed to go to the next commit stay in the staging area. Like, suppose you are working on that previous project and you have upgraded the index.html file but somehow you broke the engine.js file, so now you will just add the index.html file to stage area so it can be added to the next commit and the engine.js will be used from a previous version. And as you have not staged the broken engine.js file, the broken fill will not be committed.&nbsp;
&lt;|AD|&gt;
<ul>
<li style="font-weight: 400;">
<h5>Git Repository:&nbsp;</h5>
</li>
</ul>
Git repo is a hidden file named .git. It stores all the commits and compresses them. So when you need a specific commit it can present that to you.
<img src="https://cwh-full-next-space.fra1.digitaloceanspaces.com/videos/complete-git-tutorials-in-hindi-3/base64.webp" />
Fig: Git Three Stage Architecture
So that&rsquo;s it for Three Stage Architecture. I hope this has cleared your doubts. Thank you for watching.