Git Cheat Sheet for DevOps and Development

Day 1: Deep Dive into Git Fundamentals I’ve officially kicked off my journey through the Ultimate DevOps and Cloud Interview Guide, and Day 1 was all about mastering the backbone of collaboration: Git. While many use Git daily, today I focused on the "Why" and "How" behind common scenarios to prepare for high-level technical discussions. Here are my key takeaways from Section 2: 🔹 Fork vs. Clone: The Workflow Choice Forking: Creating a personal copy of someone else's project on GitHub to propose changes (ideal for Open Source). Cloning: Creating a local copy of a repository on my machine to start working on the code directly. 🔹 Fetch vs. Pull: Managing Data Git Fetch: The "safe" command. It downloads new data from a remote repository but doesn't integrate it into your working files. It lets you see what others have done before you commit to merging. Git Pull: A combination of git fetch followed by git merge. It’s faster but requires you to be ready for potential merge conflicts immediately. 🔹 The Goal Understanding these isn't just about running commands it's about understanding how to manage code at scale and collaborate seamlessly within a DevOps pipeline. Next up: Git Rebase vs. Merge and handling those dreaded merge conflicts! #DevOps #CloudComputing #Git #VersionControl #ContinuousLearning #TechCommunity #Upskilling Abhishek Veeramalla

🚀 Leveling Up My Git Game: Beyond the Basics After getting comfortable with Git fundamentals, I decided to go deeper and that’s where things started getting really interesting. This phase wasn’t just about commands… it was about understanding how real-world DevOps teams manage code, avoid conflicts, and ship faster. --> Here’s what I explored: - Git Merge vs Rebase Understanding the difference changed how I think about commit history. * git merge → Keeps history intact (safe & simple) * git rebase → Cleaner, linear history (but needs caution) -  Git Cherry-Pick One of the most practical features I learned! * Apply a specific commit from one branch to another * Super useful when you need a quick fix without merging everything * Helps in hotfix scenarios and selective deployments - Git Fork Learning how open-source collaboration works. Forking repositories, making changes, and contributing back via pull requests — just like real-world distributed teams. - Git Stash A lifesaver during context switching. Quickly saving uncommitted work and coming back later without losing progress. - .gitignore Small file, big impact. Preventing unnecessary files (logs, env files, build artifacts) from polluting the repo. - GitHub Pages Deployed a simple static site directly from a repo Understanding how code can go live without complex infrastructure was eye-opening. --> Key Takeaway: Git is not just a tool it’s a collaboration strategy. From handling merge conflicts to maintaining a clean commit history, these concepts are exactly what DevOps and Cloud workflows rely on. -> What’s Next? Integrating these workflows into CI/CD pipelines and automating deployments. #DevOps #Git #GitHub #VersionControl #Cloud #OpenSource #LearningInPublic #CICD #TechJourney

🚀 DevOps Journey – Day 19 / 100 Today I learned Git Tags, Fork, Merge Conflicts & Bitbucket 🔥 ⸻ 🔹 🏷️ Git Tags (Versioning) 👉 Tags are like milestones / backups in Git 📌 Example: Version1 → 3 commits Version2 → 2 more commits Version3 → 2 more commits 👉 We can mark versions like: • app-v1 • app-v2 • app-v3 ⸻ 🔹 🧪 Hands-on Example mkdir project cd project git init touch file1 file2 file3 git add file1 git commit -m "file1 commit" git add file2 git commit -m "file2 commit" git add file3 git commit -m "file3 commit" 👉 Apply tags: git tag app-v1 git tag git log 👉 Push tag to GitHub: git push origin app-v1 git push origin --tags 🔹 🍴 Git Fork 👉 Fork = Copy of someone else’s repo into your GitHub 📌 Steps: 1. Click Fork in GitHub 2. Repo copied to your account 3. Clone → Make changes → Push 💡 Used in open source contributions ⸻ 🔹 ⚠️ Merge Conflicts (Real-Time) 👉 When 2 people change same file/line → Conflict 🎬 Example: Tillu & Shanon both ask Radhika for movie at 1:30 PM 😅 👉 Same time → Conflict 💡 Solution: • Manually edit file • Remove conflict markers • Commit resolved code ⸻ 🔹 🔁 Git Alternatives • Bitbucket • Azure Repos • AWS CodeCommit ⸻ 🔹 🔵 Bitbucket Basics 👉 Same as GitHub (Repo hosting) 📌 Workflow: • Create repo • Clone repo • Create branch • Commit changes • Push & Pull ⸻ 🔹 🔐 Bitbucket Token (App Password) 📌 Steps: • Go to Settings → Access Management • Create App Password / API Token • Set permissions (read/write) • Use instead of password ⸻ 💡 Pro Tip: Use tags for releases, forks for contributions, and always resolve conflicts carefully! You’re now thinking like a real DevOps Engineer 🚀 #DevOps #Git #GitHub #Bitbucket #VersionControl #100DaysOfDevOps #LearningJourney #Cloud #Automation #RealTime #flm #frontlinemedia #reach #edutech Frontlines EduTech (FLM)

🚀 Day 2 – Git Learning Journey | Advanced Commands Continuing my DevOps preparation, today I explored some powerful Git commands that are widely used in real-time projects and interviews. 🔹 Key Concepts Covered: ⚙️ Git Config Used to set username and email for commits 🚫 .gitignore Helps exclude unnecessary files like logs, environment files, and dependencies ⏪ Git Reset Undo commits in different ways: Soft → keeps staged changes Mixed → keeps working directory Hard → removes everything ✏️ Git Amend Modify the last commit message or content 📜 Git Reflog Tracks all Git actions and helps recover lost commits 🍒 Git Cherry-pick Copy specific commits from one branch to another 💡 These concepts are extremely useful for troubleshooting, version control, and interview preparation. 🔥 Moving forward to Day 3 – Branching & Merging #Git #DevOps #AWS #LearningJourney #VersionControl #CloudComputing #CareerGrowth #frontlinesmedia #FLM

📝 Day 6 Sharing my DevOps Series..... *git config is used to set and manage Git settings like your username, email, editor, and more. git config --global user.name "Your Name" git config --global user.email "your@email.com" *View commit history git log git log --oneline *Git Branch git branch git branch feature git checkout feature Branch = separate workspace *Git Merge - Combine changes git merge feature Merges feature branch into main Watch for conflicts *Git Clone Copy a repository git clone <repo-url> Downloads project to your system *Git Pull vs Fetch git fetch git pull Fetch = download changes Pull = fetch + merge *Git Push Upload your code git push origin main Sends commits to remote repo *Git Tag Mark important versions git tag v1.0 git push origin v1.0 Useful for releases *Git Stash Save work temporarily git stash git stash pop Useful when switching tasks *Git Rebase vs Merge Two ways to integrate code Merge → keeps history Rebase → cleaner history git rebase main *Git Fork (GitHub Workflow) Post: Contribute to open source Fork → copy repo Clone → local copy Push → your repo PR → contribute git cherry-pick git cherry-pick is used to pick a specific commit from one branch and apply it to another branch. git cherry-pick <commit-id> #GitHub #OpenSource #DevOps #git #cloud #repository.....

🚀 Beyond Git Commands — Thinking Like a Senior Engineer Most developers know how to use Git. Fewer understand how it actually works. From exploring Git’s content-addressable storage (blobs, trees, commits) to mastering concepts like rebase vs merge, revert vs reset, and detached HEAD, I deep-dived into what makes Git a powerful distributed system — not just a tool. 💡 Key takeaway: Git isn’t just version control — it’s a data structure + workflow engine + collaboration backbone for modern engineering. Understanding internals helps you: ✔ Debug faster ✔ Handle production issues safely ✔ Design scalable branching strategies ✔ Work confidently in large teams If you're preparing for interviews or aiming to level up — focus on why Git works, not just how to run commands. #Git #GitHub #DevOps #SoftwareEngineering #InterviewPrep #Cloud #LearningJourney

🚀 Day 3 – Git Learning Journey | Revert & Branching Continuing my DevOps journey, today I explored two important Git concepts used in real-time development and collaboration. 🔹 Key Concepts Covered: 🔁 Git Revert Used to undo changes by creating a new commit ✔️ Safe way to reverse changes without losing history ✔️ Best used in shared/public branches 👉 Example: git revert <commit-id> 🌿 Git Branch Branches allow parallel development without affecting the main code ✔️ Create branch → git branch feature ✔️ Switch branch → git checkout feature ✔️ Create & switch → git checkout -b feature 💡 Helps developers work independently and merge later 📊 Simple Visualization: Main Branch: A —— B —— C Feature Branch: ↳ D —— E 👉 Work happens in feature branch, then merged to main 💡 Interview Insights: Difference between git reset vs git revert What is branching in Git? Why do we use branches? How to switch branches? 🔥 Learning step by step — building strong Git fundamentals for DevOps & Cloud. #Git #DevOps #AWS #LearningJourney #VersionControl #CloudComputing #CareerGrowth #FLM #frontlinesmedia

𝗚𝗶𝘁 𝗕𝗿𝗮𝗻𝗰𝗵𝗶𝗻𝗴 𝗦𝘁𝗿𝗮𝘁𝗲𝗴𝗶𝗲𝘀 𝘀𝗼𝗺𝗲𝘁𝗵𝗶𝗻𝗴 𝗜 𝘂𝗻𝗱𝗲𝗿𝘀𝘁𝗼𝗼𝗱 𝗼𝗻𝗹𝘆 𝗿𝗲𝗰𝗲𝗻𝘁𝗹𝘆 When I started using Git, I honestly thought branching simply means "create branch, push code, done." That's it. Job over. But while working on actual projects, one thing hit me hard. The wrong branching strategy does not just cause small hiccups. It creates confusion that keeps piling up and becomes very difficult to manage later. So let me share what I understood, in simple words. 𝗠𝗮𝗶𝗻 𝗼𝗿 𝗧𝗿𝘂𝗻𝗸-𝗕𝗮𝘀𝗲𝗱 𝗗𝗲𝘃𝗲𝗹𝗼𝗽𝗺𝗲𝗻𝘁: Everyone commits directly to one main branch with small, frequent updates. Simple to follow, but it needs a lot of discipline from every single person on the team. 𝗙𝗲𝗮𝘁𝘂𝗿𝗲 𝗕𝗿𝗮𝗻𝗰𝗵𝗶𝗻𝗴: Every feature gets its own separate branch. Once the work is done, it gets merged back to main. Very easy to manage and track, and honestly the most commonly used approach in most teams I have seen. 𝗚𝗶𝘁 𝗙𝗹𝗼𝘄: This one has dedicated branches for everything, main, develop, feature, release, hotfix. Slightly more process-heavy but very useful once your project or team starts growing. 𝗥𝗲𝗹𝗲𝗮𝘀𝗲 𝗕𝗿𝗮𝗻𝗰𝗵𝗶𝗻𝗴: A separate branch is created for each release and all bug fixes are handled there before anything goes live. Very helpful when you want stable and controlled deployments. One thing I genuinely realised after all this is that there is no perfect branching strategy that works for everyone. It completely depends on your team size, your project, and how frequently you are shipping things. Personally, feature branching felt like the most natural starting point for me and I still use it quite often. #DevOps #Git #GitHub #CICD #VersionControl #CloudComputing #Docker #Kubernetes #AWS #Automation #LearningDevOps #DevOpsTips

🚀 Git Cheat Sheet – Simplified for Everyday Use If you work with code, Git is non-negotiable. Here’s a clean breakdown of the core workflow to keep things efficient and mistake-free: 🔹 Create Start your repo with git init or clone existing code using git clone. 🔹 Update Stay in sync with your team using git pull, git fetch, and git merge. 🔹 Branching Work safely by creating branches (git checkout -b) and merging when ready. 🔹 Commit Track your changes with meaningful commits using git commit. 🔹 Publish Push your work to remote repositories using git push. 🔹 Revert Made a mistake? Use git revert or git reset to roll back changes. 🔹 Inspect Understand your repo with git status, git log, and git diff. 💡 Key takeaway: Mastering just these commands covers 90% of real-world Git usage. Keep this cheat sheet handy — it’ll save you time, reduce errors, and make collaboration smoother. #Git #DevOps #SoftwareEngineering #SRE #Cloud #Learning #Tech🚀 Git Cheat Sheet – Simplified for Everyday Use If you work with code, Git is non-negotiable. Here’s a clean breakdown of the core workflow to keep things efficient and mistake-free: 🔹 Create Start your repo with git init or clone existing code using git clone. 🔹 Update Stay in sync with your team using git pull, git fetch, and git merge. 🔹 Branching Work safely by creating branches (git checkout -b) and merging when ready. 🔹 Commit Track your changes with meaningful commits using git commit. 🔹 Publish Push your work to remote repositories using git push. 🔹 Revert Made a mistake? Use git revert or git reset to roll back changes. 🔹 Inspect Understand your repo with git status, git log, and git diff. 💡 Key takeaway: Mastering just these commands covers 90% of real-world Git usage. Keep this cheat sheet handy — it’ll save you time, reduce errors, and make collaboration smoother. #Git #DevOps #SoftwareEngineering #SRE #Cloud #Learning #Tech

🚀 Day 13–15: Mastering Git & GitHub | DevOps Journey A little late in posting, but staying consistent with my learning journey 💪 Over the past few days, I focused on strengthening my understanding of Git & GitHub, which are essential tools for every developer and DevOps engineer. 🔹 What I Learned: Git fundamentals: version control, repositories, commits Complete workflow: working directory → staging → commit → push/pull Branching & merging for collaborative development Handling merge conflicts effectively Difference between git reset and git revert Importance of git reflog for recovering lost commits 🔹 Hands-on Practice: Initialized and cloned repositories Worked with branches for feature development Managed code changes using commits and pushes Simulated real-world workflows used in teams 🔹 Key Takeaways: Git is not just a tool, it’s a core skill for collaboration Writing meaningful commit messages improves project clarity Using branches ensures safe and scalable development Recovery tools like reflog are lifesavers in real projects 💡 This phase has helped me move closer to industry-level development and DevOps practices. 📌 Next Goal: Integrating Git with CI/CD pipelines and real-world projects #Git #GitHub #DevOps #LearningJourney #SoftwareDevelopment #Cloud #Engineering