# 🌟 Git Assignment – My Version Control Journey --- ## 🛠 Step 1: Checking Git Version 📌 _Before starting, I made sure Git was installed and working properly._  ✅ Output confirms the installed version of Git. --- ## 📂 Step 2: Checking Git Status 👀 _Time to check the working directory status… are there any changes?_  🔎 Git shows which files are staged, unstaged, or untracked. --- ## ➕ Step 3: Adding Files to Staging ✨ _Changes spotted! Let’s move them to the staging area with_ `git add`.  🗂 Files are now ready to be committed. --- ## 📝 Step 4: Viewing Commit History 📖 _Every project tells a story… here’s mine!_  🕒 A detailed timeline of commits, complete with author, date, and messages. --- ## 🔹 Step 5: Compact History (Oneline) 👾 _Too much detail? Let’s simplify it with_ `git log --oneline`.  ⚡ Quick and clean history view. --- ## 🌳 Step 6: Visual History (Graph) 🎨 _Why read history when you can see it?_  🌿 Branches and merges, beautifully visualized. --- ## 🔍 Step 7: Checking Differences 🖋 _Curious about what exactly changed? Enter_ `git diff`.  🔑 Shows line-by-line modifications before committing. --- ## 🆚 Step 8: Comparing Two Commits ⚔️ _What changed between two versions of history?_  📌 Helps track evolution between commits. --- ## 🌿 Step 9: Exploring Branches 🔀 _Time to branch out!_  🌱 Branches allow experimenting without breaking the main code. --- ## 📥 Step 10: Cloning a Repository 🛰 _Finally, bringing a repo from remote to local with_ `git clone`.  📂 A complete copy of the project, ready to explore and edit. --- ## 📥 Step 11: Pulling the Code 🛰 _Fetched and merged updates from the remote repository using_ `git pull origin`.  --- ## 🌐 Step 12: Checking Remote 🔗 _Verified remote repository connections with_ `git remote -v`.  --- ## 🚫 Step 13: Ignore File 📄 _Added a `.gitignore` file to exclude unnecessary files like logs or temporary data._  --- ## 📜 Step 14: Viewing File History 📖 _Checked the history of changes for a specific file using_ `git log filename`.  ✅ Shows all commits that modified the file, with author, date, and commit messages. --- ## 🕵️ Step 15: Git Blame 🔎 _Tracked who last modified each line of a file using_ `git blame filename`.  📌 Useful to identify responsibility for specific lines. --- ## 🔀 Step 16: Git Merge 🔗 _Merged changes from one branch into another using_ `git merge branchname`.  📌 Helps integrate changes from different branches into the main branch. --- ## 🌐 Step 17: Git Log (All, Oneline Graph) 📊 _Viewed a compact, visual history of all commits across branches using_ `git log --oneline --graph --all`.  📌 Great for visualizing the entire project history at a glance. --- # ✨ Wrap-Up Notes 1. ✅ **Git Version Check** – Confirmed installation. 2. ✅ **Git Status** – Checked working tree status. 3. ✅ **Git Add** – Staged changes for commit. 4. ✅ **Git Log** – Viewed commit history. 5. ✅ **Git Log (oneline/graph)** – Simplified and visual history. 6. ✅ **Git Diff** – Compared changes in files and commits. 7. ✅ **Git Branch** – Managed branches. 8. ✅ **Git Clone** – Pulled repo from remote. 9. ✅ **Git Pull** – Synced changes from remote. 10. ✅ **Git Remote** – Checked repository connections. 11. ✅ **Git Ignore** – Excluded unnecessary files. 12. ✅ **Git File History & Blame** – Tracked changes and contributors line by line. 13. ✅ **Git Merge** – Combined branch histories. 14. ✅ **Git Graph (all, oneline)** – Visualized all commits and branches. --- # ❓ Questions & Answers ### 🔢 How many commits modified this file? **Ans:** `1` --- ### 🧩 What differences do you see when adding the `-p` option? **Ans:** - Without `-p` → Only commit metadata (hash, author, date, message). - With `-p` → Shows the actual diff (patch), i.e., the lines added (`+`) or removed (`-`) in each commit. --- ### 👤 Who changed each line of the file? **Ans:** `vipinraj01` --- ### 📏 How does `-L` help when the file is large? **Ans:** It limits the log output to specific lines, e.g., shows commit history only for **lines 20–40** of the file. --- ### 📧 What extra information does `-e` provide? **Ans:** It shows the **author’s email address** alongside their name, useful when multiple contributors have the same display name.