Learning Git & GitHub for DevOps and Version Control

🚀 Day 9 of Git & GitHub Series – Master Your Git Setup Like a Pro Before writing great code… set up your Git the right way. Because clean configuration = clean commits = professional workflow. Today’s focus: Git Config & Repository Information — the small commands that make a big difference in your daily productivity. ✅ Set your identity for commits ✅ Customize your editor ✅ Enable colorful output ✅ Create powerful aliases ✅ View & manage all configs easily These aren’t just commands… They’re the difference between beginner Git users and efficient developers. 💡 Pro tip: git config --global alias.st status Once you try git st instead of git status… there’s no going back 😉 If you're serious about becoming a better developer, mastering Git configuration is non-negotiable. 📌 Save this post 📌 Practice the commands 📌 Follow the series for daily Git mastery Day by day → Repo by repo → Leveling up 🚀 #Git #GitHub #DevOps #Developers #SoftwareEngineering #CodingLife #Programmers #TechSkills #VersionControl #OpenSource #DeveloperTools #LearnInPublic #TechCareer #Cloud #100DaysOfCode #EngineeringLife

Git is at the heart of modern software development. Whether you’re working solo or collaborating with a team, mastering the core Git commands makes your workflow faster, cleaner, and safer. Here are some of the most commonly used Git commands I use on a daily basis: 🔹 git clone – Clone a remote repository to your local machine 🔹 git status – Check the current state of your working directory 🔹 git add – Stage changes for commit 🔹 git commit -m "message" – Save changes with a clear message 🔹 git pull – Fetch and merge the latest changes from the remote repo 🔹 git push – Push local commits to the remote repository 🔹 git branch – List, create, or delete branches 🔹 git checkout / git switch – Switch between branches 🔹 git merge – Merge one branch into another 🔹 git log – View commit history 🔹 git diff – Compare changes between commits, branches, or files What Git command do you find yourself using the most? 👇 #Git #DevOps #SoftwareEngineering #Cloud #VersionControl #Developers

How Git Actually Works (Simple Explanation) Many developers use Git daily. But not everyone clearly understands what happens behind the scenes. Here’s the simple flow 👇 🖥️ 𝟭. 𝗪𝗼𝗿𝗸𝘀𝗽𝗮𝗰𝗲 This is where you write and edit your code. Files are modified here. When you run: git add You move changes to the next stage. 📦 𝟮. 𝗦𝘁𝗮𝗴𝗶𝗻𝗴 𝗔𝗿𝗲𝗮 This is like a preparation zone. You choose what changes will go into the next commit. When you run: git commit Changes move into your local repository. 💾 𝟯. 𝗟𝗼𝗰𝗮𝗹 𝗥𝗲𝗽𝗼𝘀𝗶𝘁𝗼𝗿𝘆 This is your local Git history. Commits are stored here on your system. To share changes: git push → sends code to remote. To get updates: git fetch → downloads changes git pull → fetch + merge together ☁️ 𝟰. 𝗥𝗲𝗺𝗼𝘁𝗲 𝗥𝗲𝗽𝗼𝘀𝗶𝘁𝗼𝗿𝘆 This is GitHub, GitLab, or Bitbucket. It stores code online for collaboration. 💡 Simple Way to Remember: Workspace → Stage → Commit → Push Git isn’t complicated. It’s just a structured way to track and share changes safely. Once you understand this flow, Git becomes much easier. 🔖 Hashtags (SEO-friendly) #Git #VersionControl #GitHub #SoftwareDevelopment #WebDevelopment #DeveloperTips #ProgrammingBasics

🚀 Day 8 | #90DaysDevOpsChallenge 🚀 Today I learned and practiced Git installation, Git configuration, and GitHub setup using SSH 🐧💻 This is a must-have skill for DevOps, Cloud, and Software Engineers. 🧩 Git Installation & Verification 🔹 Installed Git using: sudo apt install git 🔹 Checked Git version: git --version 👉 Confirms Git is installed successfully ✅ 👤 Git User Configuration 🔹 Set global username & email: git config --global user.name "Your Name" git config --global user.email "your.email@example.com" 🔹 Verify configuration: git config --list git config --get user.name git config --get user.email 👉 This info is attached to every commit ✍️ 🔐 GitHub SSH Setup 🔹 Generated SSH key: ssh-keygen -t ed25519 -C "your.email@example.com" (Pressed Enter → Enter → Enter) 🔹 Copied public key: cat ~/.ssh/id_ed25519.pub 🔹 Added key to GitHub → Settings → SSH & GPG keys 🔹 Tested SSH connection: ssh -T git@github.com 👉 Confirms secure GitHub connection 🔐 📦 First GitHub Push (Hands-on) git init git add README.md git commit -m "first commit" git branch -M main git remote add origin git@github.com:alam-rijwan/90daysdevops-chalenges.git git push -u origin main ⚠️ Common Error Faced & Fixed ❌ Rejected – fetch first This happens when the remote repo already has changes. ✅ Solution: git pull origin main --rebase git add . git commit -m "your commit message" git push -u origin main 👉 Issue resolved successfully 🎯 💡 Key Takeaway: Git + GitHub with SSH provides secure version control, smooth collaboration, and is the foundation of CI/CD pipelines 🚀 On to Day 9 💪 #Day8 #Git #GitHub #DevOpsJourney #LearningInPublic #VersionControl #SSH #Linux #CloudComputing #90DaysDevOpsChallenge

🚀 Day 23 of #90DaysOfDevOps — Git Branching & GitHub Workflow Today I worked on one of the most important concepts in Git — Branching 🌿 This is where Git actually becomes powerful in real-world DevOps and development workflows. 🔧 What I practiced today: ✔ Creating and switching branches (git branch, git switch, git checkout) ✔ Making isolated commits on feature branches ✔ Verifying that changes don’t affect the main branch ✔ Deleting unused branches ✔ Pushing multiple branches to GitHub ✔ Understanding origin vs upstream ✔ Learning git fetch vs git pull ✔ Practicing clone vs fork workflow 💡 Key Learning: Branching allows teams to work on features, fixes, and experiments independently without breaking production code — this is the foundation of CI/CD pipelines. 🧪 Hands-on Work: Created feature branches (feature-1, feature-2) Made commits on different branches Tested branch isolation Synced changes between local and remote Practiced full GitHub workflow (push, pull, fork, clone) 📂 GitHub Repository: 👉 https://lnkd.in/g9i-KJx3 Consistency is the real game changer. Learning in public 🚀 #DevOps #Git #GitHub #Linux #Automation #LearningInPublic #90DaysOfDevOps #DevOpsEngineer #TrainWithShubham

Day 12/100 – Git & GitHub Deep Dive: Restore, Reset & Force Push 🔁🐙 Today was all about fixing mistakes in Git the right way — something every developer & DevOps engineer faces in real projects. I learned how to safely undo changes, uncommit code, and even force push when local and remote histories don’t match. 🛠️ What I did today ✔ Cloned a GitHub repository ✔ Modified files in the working directory ✔ Checked file states using git status ✔ Used git restore to discard changes ✔ Used git restore --staged to unstage files ✔ Configured Git username & email ✔ Committed changes with proper messages ✔ Explored git reset (soft, mixed & hard) ✔ Understood commit history using git log ✔ Fixed wrong commits using reset ✔ Used force push to sync local & remote branch ✔ Learned how companies handle private repos & tokens 🔁 Git File Lifecycle Working Directory → Staging Area → Commit History → Remote Repository (GitHub) 🔄 Reset Types Explained Soft Reset → Removes commit → Keeps changes staged Mixed Reset → Removes commit → Keeps changes in working directory Hard Reset → Removes commit → Deletes changes completely (⚠️ careful) 🚀 Important Commands Used gitclone <repo-url> git status # Discard local changes git restore index.html # Unstage files git restore --staged index.html # Stage & commit git add . git commit -m"Updated index.html" # View history gitlog --oneline # Reset commits git reset --soft HEAD~1 git reset --mixed HEAD~1 git reset --hard HEAD~1 # Force push git push -f origin main 🔐 Private Repository Access ✔ Companies use private repositories ✔ Cloning requires Personal Access Token (PAT) ✔ Tokens are safer than passwords ✔ Token-based access is industry standard 💡 Key Learnings ✔ Git mistakes are normal — fixing them is a skill ✔ Restore helps discard unwanted changes ✔ Reset helps fix wrong commits ✔ Force push should be used carefully ✔ Understanding Git internals = confidence at work ✔ Essential knowledge for DevOps & real projects 📌 Save this post — Git reset & force push are frequently asked in interviews. #Git #GitHub #DevOps #VersionControl #SoftwareDevelopment #CloudCareers #Linux #100DaysOfDevOps #SRTechOps

Today I strengthened my Git fundamentals 🚀 Learned and practiced the core Git commands: • git clone • git add • git commit • git push • git status • git log • git config (name & email) It may look basic… but basics build strong developers. Version control is not just about pushing code — it’s about writing clean history, collaborating better, and thinking like a professional developer. One step closer to becoming industry-ready 💻☁️ Consistency > Motivation. #Git #VersionControl #DevOps #CloudEngineer #AWSJourney #LearningInPublic #TechGrowth

SUBJECT: Git looks simple… until the first real project 😅 Most developers learn Git by memorising 3 commands: git add git commit git push And it works… until one day: ⚠ merge conflict appears ⚠ branch history breaks ⚠ commit disappears ⚠ panic starts That’s when we realise Git is not about commands — it’s about understanding version control. While improving my DevOps skills, I found a very helpful Git resource that explains things properly from beginner → professional level. It covers: ✅ How to create repositories correctly ✅ Working with branches and remotes ✅ Rebasing vs merging (when to use what) ✅ Recovering lost commits safely ✅ Real Git workflows used by teams Honestly, Git becomes much easier once the concepts are clear. Curious 👇 Which Git topic confused you the MOST when learning? 1️⃣ Merge conflicts 2️⃣ Rebasing 3️⃣ Branching strategy 4️⃣ Lost commits recovery Reply with the number 🙂 Save this post if Git ever scared you once 😄 #git #devops #github #linux #cloud #developer

🚀 Git Commands Every Developer Must Know Most beginners use git init and git clone interchangeably. 1. Git init Used when you want to create a brand-new Git repository. Command : git init What it does: 1. Creates a .git/ directory 2. Starts tracking the current folder 3. No remote repo attached by default Common use case: ✔️ New project from scratch ✔️ Local-only project ✔️ When you’ll connect a remote later Commands to know : 1. git init 2. git init folder_name 3. git init --initial-branch=main/master 4. git init --quiet 2. Git Clone Used when a repository already exists remotely (GitHub / GitLab / Bitbucket). Command : git clone <repo_url> What it does: 1. Downloads the entire repository 2. Includes full commit history 3. Automatically sets the remote (origin) 4. Ready to work immediately Common use case: ✔️ Team projects ✔️ Open-source contributions ✔️ Existing production codebases 📌 When to Use What? 👉 Use git init When starting a new project from scratch 👉 Use git clone When working on an existing repository #Git #GitCommands #VersionControl #Developer #SoftwareEngineering #DevOps #Coding #LearningJourney #TechSkills #CareerGrowth

🚀 Still confused between Git and GitHub? Let’s clear it up in 30 seconds. ✅ Git - Git is a free, open-source version control system. It runs on your local machine and helps you track changes in your code, roll back mistakes, and experiment safely. - Essentially, Git tracks your project and gives you “undo/redo” power like in a text editor. You can think of it as a “time machine” ⏳ for your projects. ✅ Github - GitHub, on the other hand, is a cloud-based hosting platform for Git repositories. It builds on top of Git and allows developers from anywhere in the world to collaborate on the same project. So in simple terms: 👉 Git is the tool. 👉 GitHub is the platform. Simple — but powerful 🚀 #Git #GitHub #VersionControl #SoftwareDevelopment #LearningJourney #CodingBasics #BuildInPublic #Git #GitHub #VersionControl #GitBasics #DevelopersOfLinkedIn  #SoftwareEngineering #CodingJourney #TechCommunity  #BuildInPublic #LearnToCode #SourceControl #ProgrammingLife