Merge pull request #238 from codeharborhub/dev-1

added git docs

Author: ajay-dhangar

absolute-beginners/git-github-beginner/collaboration/_category_.json

@@ -0,0 +1,9 @@
+{
+  "label": "Collaboration",
+  "position": 5,
+  "link": {
+    "type": "generated-index",
+    "title": "Collaboration & Open Source",
+    "description": "Learn the social side of coding. Master Pull Requests, solve conflicts, and contribute to global projects at CodeHarborHub. Discover how to collaborate effectively, manage branches, and navigate the world of open-source development. Join us on this journey to become a confident collaborator in the coding community."
+  }
+}

absolute-beginners/git-github-beginner/collaboration/clone.mdx

@@ -0,0 +1,82 @@
+---
+title: "Cloning a Repository"
+sidebar_label: "2. Cloning"
+sidebar_position: 2
+description: "Learn how to download a repository from GitHub to your local computer to start coding. This is the essential next step after forking a project and is crucial for contributing to open-source software. Master the cloning process to bring code from the cloud to your machine and begin your development journey."
+tags: ["git", "github", "cloning", "open-source", "contributing"]
+keywords: ["git", "github", "cloning", "open-source", "contributing"]
+---
+
+Once you have a repository on GitHub (either your own or a **Fork** you made), the next step is to bring that code onto your physical computer. This process is called **Cloning**.
+
+When you clone a repository, you aren't just downloading the files; you are downloading the **entire project history** and setting up a connection between your computer and the cloud.
+
+
+## What happens during a Clone?
+
+Unlike a simple "Download ZIP," `git clone` does three things automatically:
+1.  **Creates a folder** with the project name.
+2.  **Downloads every version** of every file in the project's history.
+3.  **Sets up a Remote** called `origin`, which points back to GitHub so you can push and pull changes later.
+
+## How to Clone a Project
+
+To clone a repository, you need its **URL**. You can find this on the main page of any GitHub repository.
+
+### Step 1: Get the URL
+1.  Go to the repository on GitHub.
+2.  Click the green **`<>` Code** button.
+3.  Copy the **HTTPS** URL (it looks like `https://github.com/user/repo.git`).
+
+### Step 2: Run the Command
+Open your terminal (or Git Bash) and type `git clone` followed by the URL you copied:
+
+```bash
+git clone https://github.com/codeharborhub/tutorial.git
+```
+
+### Step 3: Enter the Project
+
+After the download finishes, you must move into the new folder before you can start working:
+
+```bash
+cd tutorial
+```
+
+## Comparison: Clone vs. Download ZIP
+
+| Feature | Git Clone | Download ZIP |
+| :--- | :--- | :--- |
+| **Files** | Yes | Yes |
+| **History** | Yes (Every commit ever made) | No (Only current files) |
+| **Updates** | Easy (`git pull`) | Must download whole ZIP again |
+| **Contribution**| Ready to Push/PR | Not connected to Git |
+
+## Common Use Cases
+
+| Scenario | What to do? |
+| :--- | :--- |
+| **Joining a Team** | Get the project URL from your lead and `git clone` it. |
+| **Switching PCs** | `git clone` your own repo to your new laptop. |
+| **Learning Open Source** | Find a cool repo, `fork` it, then `clone` your fork. |
+
+## Cloning with VS Code
+
+If you prefer using a visual tool instead of the terminal, you can clone directly inside **Visual Studio Code**:
+
+1.  Open VS Code.
+2.  Press `Ctrl + Shift + P` (or `Cmd + Shift + P` on Mac).
+3.  Type **Git: Clone** and press Enter.
+4.  Paste the GitHub URL and choose a folder on your computer. VS Code will handle the cloning process for you!
+
+## Important Note for Beginners
+
+**Only clone once.** A common mistake is running `git clone` every time you want to work on a project.
+
+  * Use `git clone` the **first time** you get the project.
+  * Use `git pull` every time **after that** to get the latest updates.
+
+:::tip
+By default, Git clones the project into a folder named after the repository. If you want to name the folder something else, just add the name at the end:  
+`git clone https://github.com/user/repo.git my-custom-folder-name`
+:::

absolute-beginners/git-github-beginner/collaboration/fork.mdx

@@ -0,0 +1,72 @@
+---
+title: "Forking a Repository"
+sidebar_label: "1. Forking"
+sidebar_position: 1
+description: "Learn how to create your own personal copy of an existing project on GitHub to experiment and contribute. This is the essential first step in your journey to becoming a proficient GitHub user and open-source contributor."
+tags: ["git", "github", "forking", "open-source", "contributing"]
+keywords: ["git", "github", "forking", "open-source", "contributing"]
+---
+
+In the world of Open Source, you often find amazing projects that you want to improve or use as a starting point for your own work. However, you don't have permission to edit the original code directly. 
+
+This is where **Forking** comes in. At **CodeHarborHub**, we consider forking the first step toward becoming a true Open Source contributor.
+
+:::info
+If you are new to GitHub, forking is the best way to get your own copy of a project that you can experiment with and eventually contribute back to the original author.
+:::
+
+## What is a Fork?
+
+A **Fork** is a complete copy of a repository that is managed under **your** GitHub account instead of the original author's. It allows you to freely make changes without affecting the original project. You can then propose your changes to the original author through a **Pull Request**.
+
+### The "Notebook" Analogy
+
+Imagine your teacher has a master notebook with a great science experiment. 
+* You can't write in the teacher's notebook.
+* You **Fork** it by taking the notebook to a photocopier.
+* Now you have your own copy. you can change the steps, add drawings, or fix typos without changing the teacher's master version.
+
+## How to Fork a Project
+
+Forking is a "one-click" process that happens entirely on the GitHub website.
+
+1.  **Find the Project:** Navigate to the repository you want to fork (e.g., `github.com/codeharborhub/git-tutorial`).
+2.  **Locate the Button:** In the top-right corner of the page, click the **Fork** button.
+3.  **Configure (Optional):** GitHub will ask if you want to copy just the `main` branch or all branches. For beginners, "main branch only" is usually best.
+4.  **Create:** Click **Create Fork**.
+
+## Why do we Fork? (Use Cases)
+
+| Use Case | Description |
+| :--- | :--- |
+| **Contributing** | You found a bug in a project and want to fix it. You fork the repo, fix the bug in your copy, and then ask the owner to pull your fix. |
+| **Experimentation** | You want to try a new feature but don't want to break the original project's stable code. |
+| **Starting Point** | You found a "Boilerplate" or "Template" project that you want to use as the foundation for your own new app. |
+
+## Forking vs. Cloning
+
+It is very common for beginners to confuse these two. Here is the professional breakdown:
+
+```mermaid
+graph TD
+    A[Original Project] -- "Fork (Cloud)" --> B[Your GitHub Fork]
+    B -- "Clone (Local)" --> C[Your Computer]
+    C -- "Commit & Push" --> B
+```
+
+  * **Forking** happens on the **GitHub Server**. It creates a copy on the cloud.
+  * **Cloning** happens on **Your Machine**. It downloads the code so you can work offline.
+
+## Keeping Your Fork Up-to-Date
+
+One challenge with forking is that the original project keeps moving forward. If the original author adds a new feature, your fork won't have it automatically.
+
+To sync your fork, you can use the **Sync Fork** button on the GitHub interface of your repository:
+
+1.  Go to your forked repo on GitHub.
+2.  Click **Sync fork**.
+3.  Click **Update branch**.
+
+:::tip
+Forking is a "Public" action. Everyone can see that you forked a project, and it often shows up on your profile as a sign that you are active in the developer community!
+:::

absolute-beginners/git-github-beginner/collaboration/index.mdx

@@ -0,0 +1,71 @@
+---
+title: "Open Source Licenses"
+sidebar_label: "7. OSS Licenses"
+sidebar_position: 7
+description: "Understand the legal side of Open Source and learn how to choose the right license for your projects. This is crucial for protecting your work and allowing others to use and contribute to it. Master the art of licensing to ensure your code can be shared and built upon by the community while safeguarding your rights as a creator."
+tags: ["git", "github", "open source licenses", "collaboration", "legal", "protection", "sharing"]
+keywords: ["git", "github", "open source licenses", "collaboration", "legal", "protection", "sharing"]
+---
+
+Making a repository "Public" on GitHub does not automatically mean people can use, modify, or share your code. Without a **License**, your code is technically under "Exclusive Copyright," meaning you own it and no one else can touch it.
+
+At **CodeHarborHub**, we believe in sharing. A license is a simple text file that tells the community exactly what they are allowed to do with your work.
+
+:::info
+Think of a license like the "Terms and Conditions" for your code. It sets the rules for how others can use, modify, and share your project. Without it, your code is like a locked treasure chest that no one can open.
+:::
+
+## Why Do You Need a License?
+
+1.  **Permission:** It legally allows others to "Fork" and "Clone" your project.
+2.  **Protection:** Most licenses include a "No Warranty" clause, meaning you aren't responsible if your code breaks someone else's computer.
+3.  **Contribution:** Professional developers and companies will *never* use or contribute to a project that doesn't have a clear license.
+
+## The "Big Three" Licenses
+
+There are hundreds of licenses, but in the professional world, 90% of projects use one of these three:
+
+| License | Type | Permission Level | Summary |
+| :--- | :--- | :--- | :--- |
+| **MIT** | **Permissive** | High | "Do whatever you want, just keep my name on it." |
+| **Apache 2.0** | **Permissive** | High | Similar to MIT, but gives extra protection against patent lawsuits. |
+| **GNU GPLv3** | **Copyleft** | Medium | "You can use my code, but your project MUST also be open source." |
+
+## Which One Should You Choose?
+
+### 1. The MIT License (Recommended for Beginners)
+This is the most popular license at **CodeHarborHub**. It is short, simple, and very "friendly." It allows people to use your code in private, commercial, and open-source projects.
+* **Use it if:** You want the most people possible to use your code.
+
+### 2. The Apache License 2.0
+This is the standard for large-scale professional projects (like Android or Kubernetes). 
+* **Use it if:** You are building a serious library or tool and want to be professional about patents.
+
+### 3. The GNU GPLv3
+This is a "Restrictive" or "Copyleft" license. If someone uses your GPL code, they are legally forced to make their entire project open source too.
+* **Use it if:** You want to ensure that no one ever takes your code and makes a "secret" paid version of it.
+
+## How to Add a License to Your Repo
+
+GitHub makes this incredibly easy. You don't need a lawyer!
+
+1.  Go to your repository on GitHub.
+2.  Click **Add file** > **Create new file**.
+3.  Type `LICENSE` (all caps) as the filename.
+4.  A button will appear: **"Choose a license template"**. Click it.
+5.  Select a license (like MIT), click **Review and submit**, and commit the file.
+
+## What Happens if I Don't Choose One?
+
+If you have a public repo with **no license**:
+* People can read your code.
+* People can fork your code (because GitHub's Terms of Service allow it).
+* **But**, people cannot legally use your code in their own apps, and they cannot contribute back to you safely.
+
+> **Moral of the story:** If you want people to use your work, always add an **MIT License**.
+
+:::tip
+Not sure which one fits your specific vibe? Check out [choosealicense.com](https://choosealicense.com/). It's a simple tool created by GitHub to help you pick the perfect legal protection for your code.
+:::
+
+Now that you understand the legal side of sharing your code, you're ready to make your projects truly open source. In the next chapter, we'll dive into how to keep your fork in sync with the original project using the concept of "Upstream." This is essential for contributing to open-source projects and ensuring your code is built on the most recent version of the project. Let's get started!s

absolute-beginners/git-github-beginner/collaboration/oss-licenses.mdx

@@ -0,0 +1,80 @@
+---
+title: "Pulling and Pushing Changes"
+sidebar_label: "4. Pull & Push"
+sidebar_position: 4
+description: "Learn the daily workflow of syncing your local code with GitHub to keep your project up-to-date. Master the essential commands for pulling changes from the remote repository and pushing your work to share with your team. This is a crucial skill for collaborating effectively in any software development project."
+tags: ["git", "github", "pull", "push", "syncing", "collaboration"]
+keywords: ["git", "github", "pull", "push", "syncing", "collaboration"]
+---
+
+In a collaborative environment like **CodeHarborHub**, code is constantly moving between your computer (Local) and GitHub (Remote). To stay in sync with your team, you must master the two most frequent actions in a developer's day: **Pulling** and **Pushing**.
+
+:::important
+Pulling and Pushing are the heartbeat of any project. They keep everyone on the same page and ensure that your work is shared with the world. Master these commands to become a true collaborator at **CodeHarborHub**.
+:::
+
+## The "Daily Cycle" Concept
+
+Think of a shared **Google Doc**. 
+* **Pulling** is like refreshing the page to see what your friends wrote while you were away.
+* **Pushing** is like hitting "Save" so your friends can see what *you* just wrote. 
+
+## 1. Pulling Changes (`git pull`)
+
+**When to use it:** Every morning before you start coding, and every time a teammate tells you they've finished a feature.
+
+When you run `git pull`, two things happen:
+1. Git **Fetches** the new data from GitHub.
+2. Git **Merges** that data into your local files.
+
+```bash
+# Get the latest code from the 'main' branch on GitHub
+git pull origin main
+```
+
+## 2. Pushing Changes (`git push`)
+
+**When to use it:** After you have "Staged" and "Committed" your work locally and you are ready to share it with the world.
+
+```bash
+# Send your 'feat-login' branch to GitHub
+git push origin feat-login
+```
+
+## The "Golden Workflow"
+
+At an **Industrial Level**, we follow this 4-step loop to avoid errors and conflicts:
+
+| Step | Command | Why? |
+| :--- | :--- | :--- |
+| **1. Update** | `git pull origin main` | Start with the latest version of the project. |
+| **2. Code** | *(Work in VS Code)* | Make your magic happen. |
+| **3. Save** | `git add .` & `git commit` | Create your local "Save Point." |
+| **4. Share** | `git push origin your-branch` | Upload your work to the cloud. |
+
+## Dealing with "Rejected" Pushes
+
+Sometimes, you try to `git push` and see a scary red error message: **[rejected]**.
+
+**Why did this happen?**
+This happens because a teammate pushed code to GitHub *after* your last pull. GitHub won't let you push your work because it would overwrite your teammate's work.
+
+**The Fix:**
+
+1.  **Pull first:** `git pull origin main`
+2.  **Resolve any conflicts** (if they exist).
+3.  **Push again:** `git push origin main`
+
+## The `fetch` Alternative
+
+If you want to see what your teammates did **without** merging it into your files yet, use:
+
+```bash
+git fetch origin
+```
+
+This downloads the data but doesn't change your code. It's like "Previewing" the changes before you commit to them.
+
+:::tip
+Always **Pull before you Push**. This simple habit will save you from 90% of the merge conflicts you might face at **CodeHarborHub**.
+:::