Version Control Systems: Mastering DevOps Fundamentals with Git

🚀 Day 57 of my Learning Journey – Git Reset 📘 I explored the powerful concept of Git Reset, a command that helps developers manage and correct their commit history in Git. Understanding how to safely modify commits is an important step in becoming confident with version control systems used in modern development and DevOps workflows. 💻 📘 What is Git Reset? Git Reset is a command used to move the current branch to a specific commit. It allows developers to undo commits, unstage files, or reset the working directory to a previous state. This is especially useful when mistakes happen during commits or when we want to reorganize our commit history. ⚙️ Key Commands & Features 🔹 git reset --soft HEAD~1 Moves the branch pointer back by one commit but keeps all changes staged. 🔹 git reset --mixed HEAD~1 Resets the commit and unstages the changes, but keeps them in the working directory. 🔹 git reset --hard HEAD~1 Completely removes the last commit and deletes all related changes. Use carefully! 🔹 Reset to Specific Commit git reset <commit-id> allows moving the branch to a chosen commit in history. 🔹Unstaging Files git reset <file> removes a file from staging without deleting its changes. 🎯 Key Takeaway Learning Git Reset helped me understand how developers can safely correct mistakes and manage commit history more effectively in real development workflows. ☁️ Real-World Usage in Industry 🔹 Code Correction in Development Developers use reset to undo incorrect commits before pushing code. 🔹 CI/CD Pipeline Preparation Teams clean commit history before pushing code to automated pipelines. 🔹 Production Deployment Safety Engineers fix commit mistakes locally before changes reach production servers. 🔹 Collaborative Development Helps maintain clean and organized commit history in team projects. #Git #GitHub #DevOpsLearning #CloudComputing #LearningInPublic #TechJourney #CareerGrowth

🚀 DevOps Learning Journey - 🌿 Day 11 – Git Branching & Merging Today I learned one of the most important concepts in Git — Branching and Merging. Branching allows developers to work on new features or fixes without affecting the main codebase. 🔹 What is a Branch? A branch is a separate line of development. By default, Git has a main/master branch, and we can create new branches for features. 🔹 Why Branching is Important? ✔ Work on features independently ✔ Avoid breaking main code ✔ Enable parallel development ✔ Easy collaboration in teams 🔹 Git Commands I Practiced • git branch – List all branches • git branch feature – Create a new branch • git checkout feature – Switch to a branch • git checkout -b feature – Create & switch to branch • git merge feature – Merge branch into current branch 🔹 Example Workflow git branch feature git checkout feature # make changes git add . git commit -m "Added new feature" git checkout main git merge feature 🔹 Merge Concept Merging combines changes from one branch into another. Sometimes conflicts may occur, which need to be resolved manually. 📌 Hands-on: Created a feature branch, made changes, and merged it back to the main branch. Understanding branching is essential for working in real-world DevOps and development teams. #DevOps #Git #VersionControl #Branching #LearningJourney #ContinuousLearning

🚀 Day 60 of my Learning Journey – Git Cherry-Pick 🎯 Discovered how to copy specific commits between branches using Git Cherry-Pick. A small command, but extremely powerful when working with multiple branches in real-world projects. 📘 What is Git Cherry-Pick? Git Cherry-Pick allows you to select a specific commit from one branch and apply it to another branch. Instead of merging an entire branch, you can bring only the exact change you need. This is very useful when fixing bugs or moving small features across branches without affecting other changes. ⚙️ Key Commands & Features 🔹 git cherry-pick <commit-id> – Applies a specific commit from another branch to the current branch. 🔹 Find Commit ID using git log – Helps identify the exact commit you want to copy. 🔹 Resolve Conflicts if they occur – Similar to merge conflicts when changes overlap. 🔹 git cherry-pick --continue – Continue the cherry-pick process after resolving conflicts. 🔹 git cherry-pick --abort – Cancel the cherry-pick operation if needed. 💡 Key Takeaway Understanding Cherry-Pick helps me manage code changes more efficiently and is an important skill for working with Git in DevOps workflows. 📈 💻 Real-World Usage in Industry 🔹 Hotfix management – Developers move urgent bug fixes from development to production branches quickly. 🔹 CI/CD workflows – Teams apply critical commits to release branches without merging incomplete features. 🔹 Production stability – Only safe and verified commits are applied to production environments. 🔹 Multi-branch development – Used when maintaining different versions of software simultaneously. #Git #GitHub #DevOpsLearning #TechJourney #ContinuousLearning #SoftwareDevelopment #CareerGrowth

As I progress into learning more about Devops, here's all the things I've picked up while studying GIT this week! 🚀 Week Progress: Mastering Git & Real-World Version Control Over the past week, I’ve been focused on building a solid foundation in Git — not just using commands, but understanding how it works in real development environments. Here’s what I’ve worked through: 🔹 Core Git Workflow • Working directory → staging → commits → remote • Understanding Git as a snapshot-based system (not just file changes) 🔹 Branching & Collaboration • Creating feature branches and merging safely into main • Handling merge conflicts manually • Using GitHub workflows: fork → clone → branch → commit → push → pull request 🔹 History & Code Management • Exploring commit history with git log --oneline --graph • Using git show to inspect changes • Cleaning commit history with interactive rebase & squash 🔹 Real-World Development Practices • Using git stash to manage context switching • Understanding when to use merge vs rebase • Maintaining clean, readable commit history 🔹 Debugging & Recovery • Safe undoing with git revert vs destructive changes with git reset • Understanding detached HEAD and how to avoid losing work 💡 Key takeaway: Git isn’t just about files — it’s about managing history, collaboration, and maintaining clean, reliable codebases. This week has taken me from basic usage to confidently handling real-world workflows used in development teams. Next step: diving deeper into DevOps practices and automation 🚀 #Git #DevOps #SoftwareDevelopment #LearningInPublic #OpenToWork #CoderCo

🚀 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)

🚀 DevOps Day 21 — Git Branching & DevOps Workflow (Part 3) After fixing networking issues, I moved into real Git workflows. This is where Git becomes powerful. SSH vs HTTPS Git Connections I explored both methods: SSH Method git@github.com:nixhal33/DevOps-Mastery.git Advantages: ✔ No repeated authentication ✔ Secure ✔ DevOps-friendly HTTPS Method (Token Based) git clone https://@github.com/repo.git Steps: • Create Classic Token • Clone repo • Push changes But SSH felt more DevOps-aligned. Git Commands I Practiced ✔ git status ✔ git diff ✔ git add ✔ git commit ✔ git push ✔ git restore ✔ git revert HEAD These commands helped me: • Track changes • Revert mistakes • Monitor code differences Git Branching (Most Important Learning) Production branch: main Development branch: git checkout -b dev Workflow: Create dev branch Make changes Push to dev Merge to main Merge Conflict Practice I intentionally: • Edited files in two branches • Created merge conflict • Resolved manually • Merged successfully This was real-world Git learning. Final DevOps Insight My instructor shared something interesting: DevOps Engineers don't use Git as heavily as developers… But Git is critical for: ✔ CI/CD pipelines ✔ Automation workflows ✔ Infrastructure versioning And now I'm ready for: 🚀 Next Topic: Docker From IaC → Version Control → Containers The DevOps journey continues.  you can checkout my github repo using this link: https://lnkd.in/gjw9Fuxe #DevOps #Git #GitHub #Automation #CI_CD #InfrastructureAsCode #DockerJourney #LearningInPublic

🚀 Starting my #100DaysofDevOps Journey! Excited to begin this journey to strengthen my DevOps skills by practicing consistently and revisiting core concepts. Day 01/100 – Git Fundamentals 🔹 What I revised today: • Git is a version control system that helps track file changes and manage multiple versions efficiently • Understanding Git stages: Working Directory, Staging Area, and Repository • Difference between Local and Remote repositories • How Git maintains history of changes 🔹 Hands-on I practiced: • Initializing a repository (git init) • Tracking files (git add) • Committing changes (git commit) • Checking history (git log, git show) 💡 Key Takeaway: Understanding Git workflow and stages helps in managing code efficiently and maintaining proper version control. ⚡ Insight: Proper tracking and committing of files helps reduce confusion and keeps code organized. Day 1 ✅ | 99 more to go! #DevOps #Git #100DaysOfDevOps #LearningInPublic

Breaking the Wall of Confusion: My DevOps Journey Begins Breaking the wall of confusion isn't just a catchy phrase; it's a necessary evolution in how we build and ship software. Over the first eight sessions of my DevOps journey at @Digital Skola, I’ve moved past the surface-level tools to understand the actual friction that often exists between development and operations teams. It has become clear to me that high-performing teams don't just happen because they have a pipeline; they succeed because they’ve embraced a culture of shared responsibility where manual handoffs are replaced by automated trust. This mindset shift requires a rock-solid technical foundation, which is why mastering Linux administration and Bash scripting felt so vital during these early stages. I’ve focused on learning how to turn tedious, error-prone manual tasks into repeatable code, effectively making the terminal a primary ally in maintaining system stability. Beyond just running commands, it's about understanding the underlying networking protocols and OSI layers that ensure our services can actually talk to each other in a complex environment. Moving into containerization further changed my perspective on modern architecture. Comparing the heavy overhead of traditional Virtual Machines to the lightweight efficiency of Docker containers has redefined how I think about scalability and environment consistency. The goal is simple but profound: ensuring that what works on a developer's machine works exactly the same in production, every single time. Being part of the "Deploy Dynasty" group has only reinforced my belief that automation is the only real bridge to true innovation. I’ve compiled these technical milestones and insights into the Learning Progress Review (LPR) slides attached to this post. I invite you to swipe through and see the progress I’ve made so far in this bootcamp. #DigitalSkola #LearningProgressReview #DevOpsEngineer #BootcampDevOpsEngineer

☁️ Today’s DevOps Concept: Version Control in Infrastructure (Git + IaC) Continuing my 60‑day DevOps learning journey, today I built on yesterday’s Infrastructure as Code (IaC) concept by exploring how version control integrates with IaC. This connection is what truly transforms infrastructure into software. ✨ What I learned today: With IaC, every infrastructure change becomes a Git commit, and that unlocks some powerful advantages: 🔹 Traceability → Every change has a clear history 🔹 Collaboration → Multiple engineers can work on infrastructure safely 🔹 Review Process → Infra changes go through pull requests, just like code 🔹 Rollback Capabilities → Reverting infra becomes as easy as reverting a commit 🔹 Standardization → The entire organization follows the same templates & modules I practiced making small changes to a Terraform file, pushing it to Git, and watching how version control gives a complete picture of when and why each infrastructure change happened. Today’s biggest takeaway for me: “When your infrastructure is in Git, you gain control, visibility, and confidence.” Excited to dive into modules, state files, and automation next! #DevOps #IaC #Terraform #Git #CloudComputing #Automation #TechLearning

🚀 DevOps Multi-Cloud Learning Journey – Day 14 Today’s session was focused on advanced Git commands, which are essential for efficient version control and managing code history. Key learnings: ⚙️ git config – Configure username and email ✏️ git commit --amend – Modify last commit 🚫 .gitignore – Ignore unnecessary files 🔄 git reset (soft & hard) – Undo changes in different ways 🍒 git cherry-pick – Apply specific commits 📜 git reflog – Track all Git activities 🔍 git log -p – View detailed commit changes These concepts help in better control, debugging, and managing project history in real-time development. Frontlines EduTech (FLM) #DevOps #Git #VersionControl #AWS #CloudComputing #LearningJourney #TechSkills #ContinuousLearning #FrontlinesEduaTech #FLM