Pathlavath Chanti’s Post

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

Understanding Git & GitHub Workflow as a DevOps Engineer 🚀 Here’s how I manage code efficiently using Git 👇 🔹 Basic Workflow: git clone → Copy repo to local git checkout -b feature-branch → Create new branch git add . → Stage changes git commit -m "message" → Save changes git push origin branch → Push to GitHub Create Pull Request (PR) Code review → Merge to main 🔹 Why this matters: ✅ Avoids code conflicts ✅ Enables team collaboration ✅ Keeps production stable ✅ Supports CI/CD pipelines 🔹 What I learned: Using proper branching strategy makes deployments safer and faster. Next step: Automating this workflow using Jenkins CI/CD 🚀 If you're learning DevOps, mastering Git is a must. #Git #GitHub #DevOps #CICD #LearningInPublic #AWS

#Day_13 – Starting Git, GitHub & GitLab (DevOps Journey) Today, I started learning Git, GitHub, and GitLab, and this is one of the most important steps in my DevOps journey. 👉 Version control is not optional… it is a must for every developer and DevOps engineer. 🔹 What is Git? (Basic Understanding) Git is a version control system that helps track changes in code. Keeps a history of all changes Helps in teamwork Easy to go back to previous versions 👉 It is like a “save + history + backup system” for code. 🔹 Basic Git Commands git init – start a new repository git status – check current state git add . – add files to staging git commit -m "message" – save changes git log – see commit history 👉 These are the most used daily commands. 🔹 What is GitHub? GitHub is a cloud platform where we store our Git repositories. Store code online Share projects Collaborate with others 👉 It is widely used in industry. 🔹 What is GitLab? GitLab is similar to GitHub but also provides: Built-in CI/CD More control for DevOps Used in many companies 👉 Both GitHub and GitLab are important tools. 🔹 Working with Remote Repositories git remote add origin <url> git push – upload code git pull – get the latest code 👉 Helps in teamwork and syncing code. 🔹 Branching Concept git branch – create branch git checkout – switch branch git merge – merge changes 👉 Branching helps work on features without affecting the main code. 🔹 Collaboration Basics Multiple people work on the same project Use pull requests/merge requests Review code before merging 👉 This is how real companies work. 🔹 Why Git is Important in DevOps? Track every change Easy rollback Supports CI/CD pipelines Helps automation 👉 Without Git, DevOps is incomplete. What I realised today: ✔ Git is the backbone of development ✔ GitHub/GitLab make collaboration easy ✔ Version control is a must-have skill ✔ Every DevOps engineer uses Git daily 👉 Today was very important for my journey. Let’s keep learning and growing 💪 #Linux #DevOps #Git #GitHub #GitLab #Day13 #LearningInPublic #ITSkills #CareerGrowth #trainwithshubham #joshbatch10 #devopsengineer

🚀 Day 37 – Git & GitHub 🔧🌐 Today I learned about version control systems, especially Git and GitHub, which are essential tools for developers and DevOps engineers 💻 🔧 What is Git? Git is a version control system used to track changes in code. 👉 It helps to: Save versions of files Track changes Collaborate with team members 🌐 What is GitHub? GitHub is a cloud platform where we can store and manage Git repositories online. 👉 It allows: Sharing code Team collaboration Project management ⚙️ Basic Git Commands 👉 Initialize repository: git init 👉 Check status: git status 👉 Add files: git add . 👉 Commit changes: git commit -m "message" 👉 Connect to GitHub: git remote add origin <repo-url> 👉 Push code: git push origin main 🔄 Git Workflow 1️⃣ Create/modify files 2️⃣ Add changes (git add) 3️⃣ Commit changes (git commit) 4️⃣ Push to GitHub (git push) 💡 Why Git & GitHub? ✔ Track code changes easily ✔ Work with teams efficiently ✔ Backup code safely ✔ Essential for DevOps & CI/CD 📌 My Learning Today Understanding Git and GitHub gave me confidence to manage code, collaborate with teams, and work on real-time projects 🚀 💬 Hashtags #Git #GitHub #DevOps #VersionControl #CloudComputing #LearningJourney #TechSkills #WomenInTech #CloudEngineer

🚀 Day 15 – DevOps 100 Days Challenge 🚀 Today's learning dived deep into one of the most critical topics in DevOps — Git, GitHub, and Bitbucket — covering version control concepts, remote repository management, and the difference between these powerful platforms. 🌐🔧 📌 What I learned today: 🔹 Git vs GitHub vs Bitbucket  • Git — a distributed version control system (VCS) for tracking code changes locally  • GitHub — a cloud-based hosting platform for Git repositories with collaboration features  • Bitbucket — Atlassian's Git hosting platform, tightly integrated with Jira & Confluence 🔹 Source Code Management (SCM)  • Understanding SCM and why it's the backbone of every CI/CD pipeline 🔹 GitHub Actions & Webhooks  • Introduction to GitHub Actions for CI/CD automation  • How to configure webhooks to trigger Jenkins pipelines from GitHub Understanding these tools and commands is essential for every DevOps engineer working in collaborative, CI/CD-driven environments. 🔄🌿 Another great step forward — Day 16, let's go! 🚀💪 #DevOps #100DaysOfDevOps #Git #GitHub #Bitbucket #VersionControl #SCM #GitCommands #BranchingStrategy #MergeConflict #GitRebase #GitMerge #GitStash #CherryPick #GitHubActions #Jenkins #Webhooks #LearningJourney #ContinuousLearning

🚀 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

🚀 From Zero to Version Control: My Journey into Git & GitHub  In my journey toward becoming a DevOps Engineer, one of the most fundamental (yet powerful) skills I’ve been focusing on is Version Control using Git and GitHub.  At first, it felt like just “commands" but soon I realized it’s the backbone of modern software development and DevOps workflows. --> What I’ve Learned So Far:   - Understanding Version Control – tracking changes, collaboration, and code history.   - Git Basics – initializing repositories, staging, committing changes.   - Branching & Merging – working on features without breaking main code.   - GitHub – remote repositories, pushing code, pull requests, collaboration.  --> Key Commands I Practiced Daily:   - git init # Start a repository   - git clone # Copy a remote repo   - git add / git commit # Track and save changes   - git push / git pull # Sync with remote repositories   - git branch / git checkout # Work with branches   - git merge # Combine code changes  --> Why This Matters for DevOps & Cloud:   Version control is not just about code - it’s about collaboration, automation, and CI/CD pipelines. Every deployment, every infrastructure change, and every release starts here.  Learning Git has helped me understand how teams manage code at scale and how DevOps ensures smooth integration and delivery.  This is just the beginning - next step: integrating Git workflows with CI/CD tools and cloud platforms.   #DevOps #Git #GitHub #VersionControl #CloudComputing #LearningJourney #CI_CD #TechSkills

🌿 GitHub Flow vs GitFlow vs Trunk-Based Development After 10 years in DevOps, I've used all three in production. Here's the honest verdict — no fluff. Most teams pick a branching strategy by copying what a bigger company does. That's the wrong way to choose. The right strategy depends on your team size, release cadence, and risk tolerance. GitHub Flow works when: → You deploy continuously (multiple times a day) → Your team is small and moves fast → You trust your CI/CD pipeline completely → You don't need to support multiple live versions GitFlow works when: → You ship on a fixed release schedule (weekly, monthly) → You maintain multiple versions simultaneously → You have a QA stage before every release → Your team is large with clear role separation Trunk-Based Development works when: → You have a mature engineering culture → Feature flags are part of your workflow → You want the fastest possible feedback loop → You're serious about CI/CD at scale My honest take after a decade? Most teams start with GitFlow because it feels safe. They move to GitHub Flow as they mature. The best teams end up on Trunk-Based — but only when they've built the culture for it. There's no wrong answer. There's only the wrong answer for your team right now. Which one is your team using — and are you happy with it? 👇 #DevOps #SRE #GitHub #GitFlow #TrunkBasedDevelopment #CICD #SiteReliabilityEngineering #PlatformEngineering #CloudNative #SoftwareEngineering #EngineeringCulture #TechLeadership #Kubernetes #CloudOps #Automation #GitOps #BackendEngineering #Infrastructure #VersionControl #DevSecOps #ContinuousDelivery #Reliability #OpenSource #TechCommunity #Programming

Day 55/100🚀 Git Commands to Push Source Code to GitHub (Step-by-Step Guide) If you're starting your DevOps journey, one of the first essential skills is pushing your code to a GitHub repository. Here's a simple step-by-step guide to help you do it👇 📌 Step 1: Initialize Git Repository --> git init 👉 Initializes a new Git repository in your project folder. 📌 Step 2: Add Files to Staging Area --> git add . 👉 Adds all files to the staging area (ready to commit). 📌 Step 3: Commit Your Changes --> git commit-m"Initial commit" 👉 Saves your changes with a meaningful message. 📌 Step 4: Add Remote Repository --> git remote add origin <https://lnkd.in/gqtt4aAr> 👉 Connects your local repo to GitHub. 📌 Step 5: Push Code to GitHub --> git push-u origin main 👉 Pushes your code to the main branch of GitHub. 🔁 For Future Changes After making changes, just use: --> git add . --> git commit-m"your message" --> git push ⚠️ Common Issues & Fixes ✅ Error: remote origin already exists git remote remove origin git remote add origin <repo-url> ✅ Authentication Error (GitHub) 👉 Use Personal Access Token instead of password. 💡 Pro Tips Always write meaningful commit messages ✍️ Use .gitignore to exclude unnecessary files Pull latest changes before pushing: --> git pull origin main--rebase 🎯 Conclusion Mastering Git is a must-have skill for every DevOps Engineer. This simple workflow helps you manage code efficiently and collaborate with teams seamlessly. 🔁 I’m currently learning and sharing my DevOps journey. Follow for more practical DevOps content 🚀 #DevOps #Git #GitHub #LearningInPublic #Cloud #Automation #Beginners

🚀 DevOps Learning Journey – Git & GitHub Deep Dive Yesterday, I dedicated my time to revising Git and GitHub in depth as part of my ongoing DevOps learning challenge. This revision helped me strengthen my understanding of how modern development teams collaborate efficiently on a single project using version control systems. 🔍 Key Concepts I Focused On: 🔹 Version Control Basics Understanding how Git tracks changes, maintains history, and allows developers to work without affecting the main codebase. 🔹 Branching Strategy Learned how developers create separate branches (git checkout -b feature-name) to work on features independently and safely. 🔹 Collaboration Workflow Explored how multiple developers contribute to the same repository using: Clone → git clone Branch → git checkout -b Commit → git commit Push → git push Pull Requests & Code Review 🔹 GitHub Repository Management Understood how organizations manage access, maintain repositories, and ensure smooth collaboration among team members. 🔹 Merge & Conflict Handling Got clarity on merging branches and resolving merge conflicts — one of the most important real-world skills. 💡 Key Takeaway Git & GitHub are not just tools, they are the backbone of collaboration in DevOps and software development. A strong foundation here makes working in teams much more efficient and structured. #DevOps #Git #GitHub #LearningJourney #VersionControl #CloudComputing #ContinuousLearning #TechCareer