Git vs GitHub(cake version)

While talking about Git and GitHub, generally people gets confused in these two and assume these two same, but what we have to do LOL
hum toh chalo cake khane !

𝐂𝐚𝐤𝐞 𝐒𝐡𝐨𝐩 𝐚𝐬 𝐚 𝐏𝐫𝐨𝐣𝐞𝐜𝐭:

Rounit's Bakery (Project): The cake shop is a project, and the cakes you bake are the different versions or stages of the project.

𝐆𝐢𝐭 as a 𝐑𝐞𝐜𝐢𝐩𝐞 𝐁𝐨𝐨𝐤:

Recipe Book (Git): The recipe book is like Git. It keeps track of all the recipes (code) and any changes made to them over time. Each chef (developer) can have their own copy of the recipe book.

𝐆𝐢𝐭𝐇𝐮𝐛 as a 𝐂𝐞𝐧𝐭𝐫𝐚𝐥𝐢𝐳𝐞𝐝 𝐁𝐚𝐤𝐞𝐫𝐲:

Bakery Headquarters (GitHub): The bakery headquarters is like GitHub. It's a central place where all the recipe books (Git repositories) are stored. Chefs (developers) can share their recipes, collaborate on new cakes, and review each other's work.

𝐁𝐫𝐚𝐧𝐜𝐡𝐞𝐬 as 𝐃𝐢𝐟𝐟𝐞𝐫𝐞𝐧𝐭 𝐂𝐚𝐤𝐞 𝐅𝐥𝐚𝐯𝐨𝐫𝐬:

Cake Flavors (Branches): Imagine you have different branches for different cake flavors. Each branch represents a different development path or feature. For example, there's a "Chocolate" branch and a "Vanilla" branch.

𝐂𝐨𝐦𝐦𝐢𝐭𝐬 a 𝐂𝐚𝐤𝐞 𝐑𝐞𝐜𝐢𝐩𝐞𝐬:

Cake Recipe (Commit):

Each commit is like a specific recipe in the recipe book. It represents a snapshot of the cake at a particular point in time. Chefs (developers) can add new recipes (commits) to the book as they make changes to the cake.

𝐏𝐮𝐥𝐥 𝐑𝐞𝐪𝐮𝐞𝐬𝐭𝐬 as 𝐂𝐚𝐤𝐞 𝐑𝐞𝐯𝐢𝐞𝐰𝐬
Cake Review (Pull Request): When a chef (developer) finishes baking a new cake layer or toppings (feature), they can submit it for review. This is like creating a pull request. Other chefs can review the cake, suggest changes, and decide whether to merge the new flavor into the main collection.

Cake khate raho, seekhte raho!

Follow #rounitsinha