Shivani Shetty’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)

🚀 Day 9/100 – Git Fundamentals (Clone, Commit, Push) If you're in DevOps or development, Git is not optional… it’s your daily driver 🚗 Let’s break down the 3 most important commands 👇 🔍 What is Git? Git is a version control system that helps you track changes in your code and collaborate with others. ⚙️ 1. git clone – Get the code git clone https://lnkd.in/gG8mt6kE 👉 Copies a remote repository to your local machine ✍️ 2. git commit – Save your changes git add . git commit -m "Added new feature" 👉 Captures a snapshot of your changes 💡 Think of it as a save point in your project 🚀 3. git push – Upload your changes git push origin main 👉 Sends your commits to the remote repository 🔄 Complete Flow git clone → make changes → git add → git commit → git push 👉 That’s your daily DevOps workflow 🔁 💡 Why Git Matters ✅ Track changes ✅ Collaborate with teams ✅ Rollback if something breaks ✅ Integrates with CI/CD pipelines ⚠️ Common Mistakes ❌ Forgetting git add before commit ❌ Pushing directly to main branch ❌ Writing unclear commit messages ❌ Merge conflicts panic 😅 📌 Key Takeaway 👉 Clone → Work → Commit → Push Master this flow and you’ve mastered Git basics. 💬 What’s your most used Git command daily? #Git #DevOps #VersionControl #CI_CD #100DaysOfDevOps #LearningInPublic

*Day 2 Highlights: Git & GitHub – Version Control and Collaboration* Had an insightful session focused on the fundamentals of Git and GitHub, essential tools for modern software development and DevOps practices. 🔹 *Git Fork vs Clone* * *Fork*: Create a copy of a repository within GitHub (cloud → cloud) * *Clone*: Download repository from GitHub to local system (cloud → local) * Forking is ideal when you want to experiment or contribute to someone else’s project 🔹 *Branching Strategy* * main/master → Production-ready code * Feature branches → Isolated development (e.g., feature-alarm-jira123) * 🚫 Avoid direct changes to the main branch 🔹 *Pull Request (PR) Workflow* 1. Create a feature branch 2. Develop and commit changes 3. Raise a Pull Request 4. Code review & discussion 5. Approval and merge into main branch 👉 This workflow ensures code quality, collaboration, and controlled deployments 🔹 *Essential Git Commands* * git init – Initialize repository * git status – Check file status * git add – Stage changes * git commit -m – Commit with message * git push – Upload code * git pull – Fetch latest updates * git clone – Copy repository locally * git config – Set username & email 🔹 *Key GitHub Features* * *Issues* → Track bugs & tasks * *Projects* → Manage workflows * *Wiki* → Documentation * *Insights* → Contribution analytics * *Settings* → Permissions & controls 🔹 *Best Practices* ✔ Always work on feature branches ✔ Use Pull Requests for collaboration ✔ Write meaningful commit messages ✔ Configure Git properly before starting ✔ Leverage GitHub UI for most operations 🔹 *Advanced Concepts (Overview)* * Git Rebase → Cleaner commit history * Git Stash → Temporary work storage * Merge Conflicts → Handling code overlaps 💡 Strong version control practices are the backbone of efficient team collaboration and scalable software delivery. #DevOps #Git #GitHub #VersionControl #LearningJourney #SoftwareDevelopment #vikasratnawat #cloudDevopsHub

Have you ever accidentally deleted your codebase and wished you could go back in time? I have. And that moment of panic is exactly what made Git click for me. Not as a tool. As a lifeline. hey! I am Saurabh — currently building Acquisitions, a DevOps project I started to develop a real DevOps mindset. Not just to learn commands. But to understand why things are done the way they are in professional teams. And it all starts with Git and GitHub. Before Docker. Before CI/CD. Before deployment pipelines. Everything begins with version control. Here is what I have been learning and actually practicing: Core Git & GitHub: git init — start tracking your project git add + git commit — snapshot your progress Branching — work on features without breaking main Pull Requests — how teams review code before merging Collaboration — multiple developers, one codebase, zero chaos How it connects to DevOps: ``` Write code → Commit locally → Push to GitHub → CI/CD pipeline triggers → Tests run automatically → App deploys ``` This is not just theory. This is how every real team ships software. What hit me most: Git is not just about saving code. It is about trust — trusting that you can experiment, break things, and always come back. GitHub link:- https://lnkd.in/dnr-APMK More DevOps content coming as I keep building. ↑ This diagram shows exactly how it all connects. Save it for reference. #DevOps #Git #GitHub #BuildInPublic #developer #LearningJourney

Git in Real Life: When I started using Git, I thought it’s just for pushing code. But in real production environments, Git becomes the single source of truth. Let me share a real-world scenario Scenario: Production Issue One day, a critical service started failing after deployment. Everything looked fine in CI/CD, but users were facing errors. First step? Not logs… Git history. Using: git log --oneline We traced a recent commit where a config file was modified. Use Case: Root Cause Analysis We compared changes using: git diff <commit-id> Found that: - Environment variable was changed - API endpoint misconfigured A small change, but huge impact. Fix Strategy Instead of manually fixing, we rolled back safely: git revert <commit-id> git push origin main Production stabilized within minutes Daily Use Cases of Git in DevOps - Managing infrastructure code (Terraform, Kubernetes YAMLs) - Version controlling CI/CD pipelines - Tracking configuration changes - Enabling team collaboration - Supporting GitOps workflows Must-Know Commands (Real Usage) git clone <repo> git checkout -b feature-branch git add . git commit -m "feature update" git push origin feature-branch git pull origin main git merge main Troubleshooting Scenarios 1. Merge Conflict git pull origin main Fix conflicts manually → then: git add . git commit -m "resolved conflict" 2. Wrong Commit Made git reset --soft HEAD~1 3. Lost Changes git stash git stash apply 4. Check Who Changed What git blame <file> Key Learning Git is not just a tool. It’s your safety net, audit system, and collaboration engine. In production, debugging often starts from Git, not from code. Final Thought A single commit can: - Break production - Or save hours of debugging So always: Commit smart. Review carefully. Deploy confidently. #Git #DevOps #Troubleshooting #VersionControl #Cloud #Git Lab #MLOPS #devsecops

📝 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.....

📝 Day 5 of Sharing my DevOps Series... *Git Basics What is Git? Git is a distributed version control system used to: Track code changes Collaborate with teams Manage project history *Why Git is Used? Track code changes Maintain version history Work with multiple developers Rollback to previous versions Work in parallel using branches *Git Architecture Working Directory Where you create/edit/delete files Staging Area Middle layer between working directory & Local repository Stores changes before commit Git Repository Stores all versions, history & metadata Initialize repository git init Check status git status Add file to staging git add file.txt Commit changes git commit -m "First commit" *File States in Git Untracked → New file (not added) Modified → Changed but not staged Staged → Ready to commit *Commands ls # List files ls -a # Show hidden files mkdir folder # Create directory cd folder # Change directory *Git Commit Options git commit -m "message" # Normal commit git commit -am "message" # Add + commit (tracked files only) *What is a Branch? A branch in Git is used to work on features independently without affecting the main code. *List Branches git branch - Shows all available branches Create a New Branch - git branch dev Creates a new branch named dev *Switch Branch git checkout dev git switch dev Move from one branch to another Create + Switch (Shortcut) git checkout -b feature Delete Branch git branch -d dev Deletes branch (safe delete) git branch -D dev Rename Branch git branch -m old-name new-name Rename a branch View All Branches (Local + Remote) git branch -a *Git Logs git log # Full history git log --oneline # Short history *Remote Repository (GitHub) git remote add origin <repo_url> git push origin master- Push local commits to remote repository *main information about git: git init → Initialize repo git add → Stage changes git commit → Save changes git status → Check status git branch → Manage branches git merge → Combine branches git push → Upload to remote git clone → Copy repo #DevOps #CareerGrowth #Cloud #AWS #Infrastructure #CloudComputing #AWS #TechLearning #DevOps #LearningInPublic #TechJourney #git #github

Git Series Finale: From Commands to Architecture — The Full 10-Day Roadmap 🏆 Today marks the end of my 10-Day Git Mastery Series. What started as learning basic commands evolved into understanding the high-level architecture required for enterprise-grade DevOps. Here is the complete blueprint of everything I’ve mastered: Phase 1: The Foundation (Days 1–3) Version Control Philosophy: Understanding why Git is the backbone of modern software reliability. The Three States: Mastering the flow between the Working Directory, Staging Area, and Local Repository. Branching Strategy: Implementing isolated feature branches to protect the production codebase. Phase 2: Collaboration & Conflict (Days 4–6) 3-Way Merges: Moving beyond simple linear updates to complex team integrations. Conflict Resolution: Developing the surgical precision needed to manually fix code collisions using editors like vi or nano. Recursive (ORT) Strategy: Understanding how Git logically determines the "Ostensibly Recursive Twin" during merges. Phase 3: The Safety Net (Days 7–8) Reset vs. Revert: Choosing between "destructive" history wiping and "auditable" professional reversals. Git Rebase: Rewriting history to maintain a perfectly linear, clean project timeline—the gold standard for senior engineers. Phase 4: Optimization & Release (Days 9–10) Squashing Commits: Consolidating messy development logs into single, high-impact feature commits. Git Stash: Mastering the "pause button" to switch priorities without losing uncommitted work. Annotated Tags: Creating official production release markers (v1.0, v2.0) for deployment audit trails. Engineering Reflection This series wasn't just about syntax; it was about System Integrity. In DevOps, Git is the source of truth. Mastering it means ensuring that every line of code is tracked, every mistake is reversible, and every release is documented. #GitMastery #DevOpsEngineer #100DaysOfCode #SoftwareArchitecture #VersionControl #GitWorkflow #CareerGrowth #TechCommunity

The best git branching strategy for continuous delivery https://lnkd.in/gJXBfXd8 When choosing a Git branching strategy for continuous delivery, you need a process that provides structure without bottlenecks and speed without chaos. GitHub flow strikes the right balance.

🚀 DevOps Journey – Day 18 / 100 Today I learned real-time Git workflow with multiple developers + GitHub repo management 🔥 ⸻ 🔹 🧑💻 Real-Time Scenario 👨💻 Dev1 → Already developed code & pushed to GitHub 👨💻 Dev2 → New joiner (no code in local system) 👉 What should Dev2 do? ✔️ Clone the Repository • git clone <repo_url> → Entire code + history comes to local ⸻ 🔹 🔄 Clone vs Pull ✅ Clone • First time download • Full repo + all branches ✅ Pull • Get latest changes • Used after clone 💡 Pull = Fetch + Merge ⸻ 🔹 🌿 Branch & Sync • git branch -a → Show local + remote branches 👉 Workflow: 1. Make changes locally 2. git push → Send to GitHub 3. Other dev makes changes 4. git pull → Get updates ⸻ 🔹 🔍 Fetch vs Merge • git fetch origin branch → Check new commits (no merge) • git merge origin/branch → Merge changes into local ⸻ 🔹 ⚙️ GitHub Repository Settings 📌 You can manage repo using UI: • Rename repository • Change default branch • Change visibility (Public → Private) • Transfer ownership • Archive (read-only mode) • Delete repository (Danger Zone ⚠️) ⸻ 🔹 🆚 Git vs GitHub • Git → CLI tool (local system) • GitHub → Web UI (remote repo hosting) ⸻ 💡 Pro Tip: Every developer should know this flow: 👉 Clone → Work → Push → Pull → Repeat This is how real companies work 🚀 #DevOps #Git #GitHub #Linux #VersionControl #100DaysOfDevOps #LearningJourney #Cloud #Automation #RealTime #frontlinemedia #flm #DevSecOps #MultiCloud