<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Lakkimsetti Eswar Sai Kumar on Medium]]></title>
        <description><![CDATA[Stories by Lakkimsetti Eswar Sai Kumar on Medium]]></description>
        <link>https://medium.com/@eswarsaikumar2?source=rss-50cc6c084d2f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*BxP2LUl3sYK8Hr9MQXWnyg.jpeg</url>
            <title>Stories by Lakkimsetti Eswar Sai Kumar on Medium</title>
            <link>https://medium.com/@eswarsaikumar2?source=rss-50cc6c084d2f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 22:55:22 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@eswarsaikumar2/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Frequently Used Linux Commands in DevOps]]></title>
            <link>https://medium.com/@eswarsaikumar2/frequently-used-linux-commands-in-devops-c9bc8b70d547?source=rss-50cc6c084d2f------2</link>
            <guid isPermaLink="false">https://medium.com/p/c9bc8b70d547</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[linux]]></category>
            <dc:creator><![CDATA[Lakkimsetti Eswar Sai Kumar]]></dc:creator>
            <pubDate>Sun, 18 May 2025 14:39:35 GMT</pubDate>
            <atom:updated>2025-05-18T14:41:43.589Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sCpw_OghQ04j9t5ojm_hbg.png" /></figure><p>Whether you’re a beginner just stepping into the world of DevOps or a seasoned professional, mastering essential Linux commands is crucial. These commands help automate tasks, navigate file systems, manage configurations, and interact with remote servers. Here’s a curated list of frequently used Linux commands every DevOps engineer should know.</p><h3><strong>📍 Navigation &amp; File System</strong></h3><ol><li><strong>pwd </strong>→<strong> </strong>Print Working Directory</li><li><strong>cd </strong>→ Change Directory (Used to navigate to a different directory)</li><li><strong>ls </strong>→ List Directory Contents (Lists files and directories in the current location)</li><li><strong>ls -l </strong>→ Long listing with permissions</li><li><strong>ls -a </strong>→ Includes all files(hidden files also)</li></ol><p><strong>📜 File Operations</strong></p><ol><li><strong>history</strong> → Command History (Displays previously executed commands)</li><li><strong>touch file_name</strong> → Create an Empty File</li><li><strong>cat file_name</strong> → View File Contents</li><li><strong>cat &gt; file_name</strong> → Create/Overwrite File (after updating file press Ctrl+D to save and exit)</li><li><strong>cat &gt;&gt; file_name</strong> → Appends content to an existing file without overwriting.</li><li><strong>rm file_name </strong>→ Delete a file</li><li><strong>mkdir directory_name</strong> → Create Directory</li><li><strong>rm -r directory_name</strong> → Remove Directory and Its Contents</li><li><strong>cp &lt;source_file&gt; &lt;destination_path&gt;</strong> → Copy File to a Location(like copy + paste)</li><li><strong>mv &lt;source_file&gt; &lt;destination_path&gt;</strong> → Move or Rename File (like cut + paste)</li></ol><h3><strong>🔍 Searching and Filtering</strong></h3><ol><li>grep → Search Text in Files (grep “error” log.txt)</li><li>Piping | → The pipe sends output of one command to another (Ex: cat /etc/passwd | grep “root”) 1st command output will be input for 2nd command. We use ‘|’ between commands.</li><li>cut → Extract Columns (get fragments of a text using delimiter)Ex: cut -d “delimiter” -f1 (f1 represents 1st fragment)</li><li>awk → Advanced Text Processing. Ex: cat /etc/passwd | awk -F “:” ‘{print $1F}’ == get all the names of the users</li></ol><h3>🌐 Downloading Files</h3><ol><li>wget &lt;url&gt; → Download Files from the Internet</li><li>curl &lt;url&gt; → Transfer Data from URLs(get text present in url directly on to the terminal)</li></ol><h3>📁 Reading Logs and Content</h3><ol><li>head file_name → gives First 10 Lines of File</li><li>tail file_name → Last 10 Lines of File</li></ol><h3>📝 Editing with Vim</h3><p>vim &lt;file_name&gt; → Open the file in <strong>vim</strong> text editor.</p><p><strong>In Vim:</strong></p><ul><li>Press “<strong>i</strong>” to enter insert mode</li><li>Press “<strong>Esc</strong>” to exit insert mode</li></ul><p><strong>Saving and Exiting:</strong></p><ul><li><strong>:wq</strong> → write and quit</li><li><strong>:q</strong> → quit</li><li><strong>:q!</strong> → force quit without saving</li><li><strong>:set nu</strong> → show line numbers</li><li><strong>:set nonu</strong> → hide line numbers</li></ul><h3><strong>🟡 Vim Colon Mode Commands</strong></h3><ol><li><strong>:/word-to-find </strong>→ Searches for the word from the <strong>top</strong> and highlights it if found.</li><li><strong>:?word-to-find</strong> → Searches for the word from the <strong>bottom</strong> and highlights it.</li><li><strong>:noh</strong> → Removes the highlight from the search result.</li><li><strong>:s/bin/BIN</strong> → Replaces the first occurrence of bin with BIN in the <strong>current line</strong>.</li><li><strong>:%s/bin/BIN</strong> → Replaces the first occurrence of bin with BIN in <strong>every line</strong>.</li><li><strong>:%s/bin/BIN/g</strong> → Replaces <strong>all occurrences</strong> of with BIN in the entire file.</li><li><strong>:10s/bin/BIN</strong> → Replaces the <strong>first occurrence</strong> of bin with BIN in <strong>line 10</strong>.</li><li><strong>:10s/bin/BIN/g</strong> → Replaces <strong>all occurrences</strong> of bin with BIN in <strong>line 10</strong>.</li><li><strong>:%d</strong> → Deletes everything in the file.</li></ol><h3>🟢 Vim Escape Mode Commands</h3><ol><li><strong>u</strong> → Undo the last change.</li><li><strong>yy</strong> → Copy the current line.</li><li><strong>p</strong> → Paste the copied or cut line.</li><li><strong>10p</strong> → Paste the copied/cut content <strong>10 times</strong>.</li><li><strong>dd</strong> → Cut (delete) the current line.</li><li><strong>Shift+G</strong> → Move the cursor to the <strong>bottom</strong> of the file.</li><li><strong>gg</strong> → Move the cursor to the <strong>top</strong> of the file.</li></ol><h3>🔐 File Permissions &amp; chmod</h3><p>Linux file permissions are represented using <strong>Read (r), Write (w), and Execute (x)</strong> rights:</p><ul><li><strong>Read (r) = 4</strong></li><li><strong>Write (w) = 2</strong></li><li><strong>Execute (x) = 1</strong></li></ul><p>You can sum the values to define access levels: 7 (rwx), 6 (rw-), 5 (r-x), 4 (r--), etc.</p><p><strong>Example Permission Format:</strong></p><p>user → group → others</p><p><strong>Modifying Permissions with chmod</strong></p><ol><li><strong>chmod o+x file1</strong> → Give execute to others</li><li><strong>chmod g+x file2</strong> → Give execute to group</li><li><strong>chmod u+x file3</strong> → Give execute to user</li><li><strong>chmod g-x file2</strong> → Remove execute from group</li><li><strong>chmod ugo+rwx file4 </strong>→ Give full access to everyone</li><li><strong>chmod 765 file1 </strong>→ rwx (7) for user, rw (6) for group, rx (5) for others</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c9bc8b70d547" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Terraform State Management: Local State, Remote State with S3 and Locking with DynamoDB]]></title>
            <link>https://medium.com/@eswarsaikumar2/terraform-state-management-local-state-remote-state-with-s3-and-locking-with-dynamodb-bc3a7b9a24f4?source=rss-50cc6c084d2f------2</link>
            <guid isPermaLink="false">https://medium.com/p/bc3a7b9a24f4</guid>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[terraform]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Lakkimsetti Eswar Sai Kumar]]></dc:creator>
            <pubDate>Fri, 16 May 2025 13:57:02 GMT</pubDate>
            <atom:updated>2025-05-16T13:57:02.163Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1d0-f2ektG1oRJ_nfQagZQ.png" /></figure><p>Terraform is a powerful Infrastructure as Code (IaC) tool, and managing its state correctly is critical. In this blog, we’ll explore local state, remote state using AWS S3, the role of <strong>.tfstate</strong> and <strong>.terraform.lock.hcl</strong> files, the <strong>terraform refresh</strong> command, and how to use DynamoDB for state locking.</p><p><strong>What is Terraform State?</strong></p><p>Terraform <strong>tracks infrastructure</strong> using a state file. This file keeps a snapshot of the current infrastructure, including resource IDs, attributes, and metadata. Without it, Terraform wouldn’t know what exists in your environment.</p><p><strong>Local State</strong></p><p>By default, Terraform saves state locally in a file called <strong>terraform.tfstate</strong>. This works for small-scale or personal projects.</p><p><strong>Limitations of Local State:</strong></p><ul><li>No support for team collaboration.</li><li>No locking mechanism.</li><li>Higher risk of data loss if the file is deleted or corrupted.</li></ul><p><strong>Remote State with S3</strong></p><p>To solve the above problems, Terraform supports remote state. The most popular option is <strong>storing the state file in an AWS S3 bucket.</strong></p><p><strong>Advantages of Remote State:</strong></p><ul><li>Shared access for team members.</li><li>Centralized and secure storage.</li><li>Supports versioning and backup.</li><li>Enables state locking.</li></ul><p><strong>State Locking with DynamoDB</strong></p><p>When multiple users apply changes at the same time, state corruption can happen. To prevent this, Terraform can use an <strong>AWS DynamoDB table to lock the state file.</strong></p><p><strong>DynamoDB Table Requirements:</strong></p><ul><li>Table name: terraform-lock-table</li><li>Partition key: <strong>LockID</strong> (string)</li></ul><p>Terraform will automatically handle acquiring and releasing the lock.</p><p><strong>What is .tfstate File?</strong></p><p>The <strong>.tfstate</strong> file stores the actual state of infrastructure. It’s a JSON file updated after every terraform apply. It maps Terraform configuration to real-world resources.</p><p><strong>Important:</strong></p><ul><li>Do not edit this file manually.</li><li>Treat it as sensitive; it may contain secrets.</li></ul><p><strong>What is .terraform.lock.hcl?</strong></p><p>This file locks provider versions used in the project. It ensures consistent behavior across machines and environments.</p><p><strong>Why it’s important:</strong></p><ul><li>Prevents breaking changes from provider updates.</li><li>Should be committed to version control.</li></ul><p><strong>What is terraform refresh?</strong></p><p>terraform refresh updates the state file by querying the real infrastructure.</p><p><strong>Use cases:</strong></p><ul><li>When manual changes were made outside Terraform.</li><li>To synchronize the state with actual infrastructure.</li></ul><p>Note: This command does not change the infrastructure — only updates the state.</p><p><strong>Best Practices</strong></p><ul><li>Use remote state for teams and production.</li><li>Enable locking with DynamoDB.</li><li>Use S3 versioning to track changes.</li><li>Never edit <strong>.tfstate</strong> manually.</li><li>Commit <strong>.terraform.lock.hcl</strong> to version control.</li></ul><p><strong>Conclusion</strong></p><p>Managing Terraform state effectively is crucial for infrastructure reliability and team collaboration. Local state is good for quick tests, but remote state with S3 and DynamoDB locking is essential for real-world use.</p><p>Take the time to set up remote backends and locking — it’s worth it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bc3a7b9a24f4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Don’t Reset, Revert! A Beginner-Friendly Guide to Fixing Git Mistakes]]></title>
            <link>https://medium.com/@eswarsaikumar2/dont-reset-revert-a-beginner-friendly-guide-to-fixing-git-mistakes-4532c1aad08a?source=rss-50cc6c084d2f------2</link>
            <guid isPermaLink="false">https://medium.com/p/4532c1aad08a</guid>
            <category><![CDATA[git]]></category>
            <category><![CDATA[github]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Lakkimsetti Eswar Sai Kumar]]></dc:creator>
            <pubDate>Fri, 16 May 2025 12:24:55 GMT</pubDate>
            <atom:updated>2025-05-16T12:24:55.714Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BS28o3ptngeYNHZQIegT1Q.png" /></figure><p>“To err is human, to revert is Git.”<br>If you’ve ever made a mistake in your Git history, your first instinct might be to use git reset. But what if you want to undo a commit without losing history? That’s where git revert shines.</p><p>I’ll walk you through how git revert works, when to use it, and how it’s different from git reset with examples.</p><h3>💡 What is git revert?</h3><p><strong>git revert</strong> is used to <strong>undo a previous commit by creating a new commit</strong> that reverses the changes introduced by the original one.</p><p>🛑 Unlike git reset, <strong>it doesn’t remove the commit from history</strong> — it keeps your commit history safe and intact.</p><h3>✅ When Should You Use git revert?</h3><ul><li>When you’ve already pushed the commit to a shared repository.</li><li>When you want a safe and trackable undo.</li><li>When working in collaborative projects (Get to track what was the mistake done by commit history).</li></ul><p><strong>⚙️ How It Works (Visually)</strong></p><p>Let’s say your Git history looks like this:</p><p>A — B — C — D ← HEAD (latest commit)</p><p>If you run: <strong>git revert D</strong></p><p>Git creates a new commit E that reverses the changes in D:</p><p>A — B — C — D — E ← HEAD</p><p>Commit D is still there, but now E cancels it out.</p><h3>🧪 Step-by-Step Example</h3><p>Let’s say you’ve made a few commits:</p><p>echo “Line 1” &gt; notes.txt <br>git add . <br>git commit -m “Add Line 1”</p><p>echo “Line 2” &gt;&gt; notes.txt <br>git add . <br>git commit -m “Add Line 2”</p><p><strong>Now your file looks like:</strong></p><p>Line 1 <br>Line 2</p><p><strong>😬 Oops! You want to undo “Add Line 2”</strong></p><p>git log — oneline <br># e3b0c Add Line 2 <br># a1c2e Add Line 1</p><p>Run: <strong>git revert e3b0c</strong></p><p>Git opens an editor to confirm the commit message (you can save and close).<br> Now a new commit is created that removes Line 2 from the file.</p><h3>🔚 Conclusion</h3><p>git revert is a safe, powerful, and collaboration-friendly way to undo changes in Git. Instead of rewriting history, it adds a new step that corrects the past.</p><p>So the next time you want to undo a mistake without breaking things, don’t panic — revert it.</p><h3>✍️ Ready to Try It?</h3><p>Practice on a dummy repo and see how git revert feels in real action. Once you understand it, you’ll feel a lot more confident managing your Git history!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4532c1aad08a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ Mastering git reset(soft, mixed and hard)A Beginner-Friendly Guide]]></title>
            <link>https://medium.com/@eswarsaikumar2/mastering-git-reset-soft-mixed-and-hard-a-beginner-friendly-guide-7f99f25ed197?source=rss-50cc6c084d2f------2</link>
            <guid isPermaLink="false">https://medium.com/p/7f99f25ed197</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[github]]></category>
            <category><![CDATA[git]]></category>
            <dc:creator><![CDATA[Lakkimsetti Eswar Sai Kumar]]></dc:creator>
            <pubDate>Fri, 16 May 2025 11:39:22 GMT</pubDate>
            <atom:updated>2025-05-16T11:50:06.109Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*evv2jbSbOMkiX53g-H1_Nw.png" /></figure><p>If you’re using <strong>Git</strong> regularly, you’ve likely come across the <strong>powerful but slightly scary command: git reset.</strong> Whether you&#39;re cleaning up your <strong>commit history or undoing a mistake</strong>, git reset can be your best friend <em>or</em> your worst nightmare.</p><p>I’ll break down the three modes of <strong>git reset (soft, mixed and hard)</strong> with a practical, step-by-step example to make everything crystal clear.</p><h3>📍 First: What is git reset?</h3><p>git reset is used to move the <strong>HEAD</strong> (your current branch pointer) to a different commit. Depending on the mode, it can also:</p><ul><li>Change what’s staged</li><li>Modify your working directory</li></ul><p>Before we dive deep, let’s quickly revisit the <strong>three main areas in Git</strong>:</p><ul><li><strong>Working Directory</strong>: Your current files and edits</li><li><strong>Staging Area (Index)</strong>: Changes marked for commit</li><li><strong>Repository (HEAD)</strong>: The latest snapshot saved via commit</li></ul><p><strong>🛠 Let’s Set Up a Demo Scenario</strong></p><p>We’ll use a single file <strong>project.txt</strong> and create three commits:</p><p>echo “Line 1” &gt; project.txt<br>git add .<br>git commit -m “Commit 1: Add Line 1”</p><p>echo “Line 2” &gt;&gt; project.txt<br>git add .<br>git commit -m “Commit 2: Add Line 2”</p><p>echo “Line 3” &gt;&gt; project.txt<br>git add .<br>git commit -m “Commit 3: Add Line 3”</p><p><strong>Now your file looks like:</strong></p><p>Line 1<br>Line 2<br>Line 3</p><p><strong>And your commit history is:</strong></p><p>You can see your commit history using command: git log</p><p>HEAD -&gt; Commit 3<br> Commit 2<br> Commit 1</p><p><strong>1. </strong><strong>git reset --soft HEAD~1</strong></p><h3>✅ What it does:</h3><ul><li>Removes Commit 3</li><li>Moves <strong>HEAD</strong> to Commit 2</li><li>Keeps changes from Commit 3 in the <strong>staging area</strong></li><li><strong>Does not touch</strong> your working directory</li></ul><h3>🔎 Result:</h3><ul><li><strong>project.txt </strong>still has all 3 lines</li><li>Changes are staged, ready to recommit</li></ul><p>git commit -m “New message for Line 3”</p><p>🎯 Use when: You want to change your commit message or squash commits.</p><p><strong>2.</strong> <strong>git reset --mixed HEAD~1 <em>(default)</em></strong></p><h3>✅ What it does:</h3><ul><li>Removes Commit 3</li><li>Moves <strong>HEAD</strong> to Commit 2</li><li><strong>Unstages</strong> changes from Commit 3</li></ul><h3>🔎 Result:</h3><ul><li><strong>project.txt</strong> has all 3 lines</li><li>Line 3 is no longer staged, you must <strong>git add</strong> it again before committing</li></ul><p>git add project.txt; git commit -m “New message for Line 3”</p><p>🎯 Use when: You want to re-select which changes to stage.</p><p><strong>3.</strong> <strong>git reset --hard HEAD~1</strong></p><h3>✅ What it does:</h3><ul><li>Removes Commit 3</li><li>Moves <strong>HEAD</strong> to Commit 2</li><li><strong>Deletes</strong> changes from staging</li><li><strong>Wipes out</strong> changes from your working directory</li></ul><h3>🔎 Result:</h3><ul><li><strong>project.txt</strong> only contains:</li></ul><p>Line 1<br>Line 2</p><p>🎯 Use when: You’re absolutely sure you want to throw away changes.</p><p>⚠️ <strong>Warning</strong>: This is irreversible (unless you recover the commit hash).</p><h3>✨ Final Tips</h3><ul><li>Always double-check before using hard.</li><li>Use git log and git reflog to keep track of commit history.</li><li>For undoing commits safely, explore git revert too.</li></ul><h3>🚀 Conclusion</h3><p>Understanding how git reset works will boost your confidence when working with Git. Whether you&#39;re refining your commit history or undoing errors, these three modes (soft, mixed and hard) give you powerful control over your workflow.</p><p>Have you tried git reset in your projects? Share your experiences or tips in the comments below!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7f99f25ed197" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Git Flow vs. Feature Branching: A Practical Comparison with Visual Workflows]]></title>
            <link>https://medium.com/@eswarsaikumar2/git-flow-vs-feature-branching-a-practical-comparison-with-visual-workflows-c28fb608225b?source=rss-50cc6c084d2f------2</link>
            <guid isPermaLink="false">https://medium.com/p/c28fb608225b</guid>
            <category><![CDATA[github]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[git]]></category>
            <dc:creator><![CDATA[Lakkimsetti Eswar Sai Kumar]]></dc:creator>
            <pubDate>Thu, 15 May 2025 06:29:05 GMT</pubDate>
            <atom:updated>2025-05-15T12:36:37.670Z</atom:updated>
            <content:encoded><![CDATA[<h3>Git Flow vs. Git Feature Branching: A Practical Comparison with Visual Workflows</h3><p>Version control is the heartbeat of modern software development, and Git remains the tool of choice. But how teams structure their Git workflow can significantly impact productivity, release cycles, and collaboration. Two popular models — <strong>Git Flow</strong> and <strong>Feature Branching</strong> — offer structured processes for managing code changes.</p><p>We’ll explore both approaches with visual examples and help you decide which model best suits your team.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Hhdt3Gz5JqUGFzIILNmfZw.png" /></figure><h3>🔄 What is Git Flow?</h3><p><strong>Git Flow</strong> is a branching strategy introduced by Vincent Driessen. It offers a strict branching model designed around the release process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/726/1*2tAUKcA0-vjspeHL6VMe5g.png" /></figure><ul><li>Development starts from the main branch, which always holds stable, production-ready code.</li><li>A separate <strong>development branch</strong> is created to integrate all upcoming feature work.</li><li>Developers create <strong>feature branches</strong> from development branch to work on specific features in isolation.</li><li>Once a feature is complete, it is merged back into the development branch.</li><li>When a group of features is ready for deployment, a <strong>release branch</strong> is created from development branch.</li><li>Final testing, minor fixes, and version updates happen in the release branch.</li><li>The release branch is then merged into both <strong>main</strong> and <strong>development</strong> branch.</li><li>After merging, a version tag (e.g., v1.0, v2.0) is added on the main branch.</li><li>If a emergency production issue occurs, a <strong>hotfix branch</strong> is created from main branch.</li><li>After fixing the issue, the hotfix is merged into both main and development branches.</li><li>All temporary branches (like feature) are deleted after merging to keep the repository clean.</li><li>This process ensures version control, isolated development, and efficient bug handling.</li></ul><h3>✅ Pros:</h3><ul><li>Clear structure and responsibilities.</li><li>Ideal for big teams and long-running projects.</li><li>Great for projects with planned release cycles.</li></ul><h3>❌ Cons:</h3><ul><li>Overhead for small teams or continuous delivery.</li><li>Complex for frequent production deployments.</li></ul><h3>🌿 What is Feature Branching?</h3><p><strong>Feature Branching</strong> is a more streamlined model. It focuses on creating a separate branch for each feature or fix from main branch, followed by pull requests and automated testing pipelines.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/732/1*6Fel22NiSS1V1Sus3v0Y1Q.png" /></figure><ul><li>Development starts from the main branch, which holds the latest stable release (e.g., v1.0.0).</li><li>Developers create <strong>feature or hotfix branches</strong> from main branch to work on specific tasks or fixes.</li><li>Work on the feature branch proceeds independently and includes stages like build, compile, unit tests, static code analysis (sonar scan, sast, dast), docker image creation, image scanning, dev deployment, functional testing.</li><li>Once development and testing are complete, a <strong>pull request (PR)</strong> is raised to merge the feature branch back into main branch.</li><li>After code review and approvals (CR Process), the PR is approved and merged.</li><li>The updated main branch enters the <strong>QA/UAT pipeline</strong>, which includes image download, environment configuration, deployment to qa/uat, integration testing, cr and jira ticketing.</li><li>Once the changes pass QA/UAT, they are promoted to the <strong>Production pipeline, which includes </strong>image download, production configuration, deployment to prod, marked as done.</li><li>Versioning is updated post-deployment (e.g., v1.1.1), ensuring traceability.</li><li>This model emphasizes <strong>short-lived branches</strong>, <strong>early testing</strong>, and <strong>continuous delivery</strong>, making it ideal for agile teams.</li></ul><h3>✅ Pros:</h3><ul><li>Simpler and more flexible.</li><li>Encourages smaller, more manageable changes.</li><li>Well-suited for continuous integration and delivery (CI/CD).</li></ul><h3>❌ Cons:</h3><ul><li>Can become chaotic with many simultaneous branches.</li><li>Lacks the formal structure of Git Flow for large-scale versioning.</li></ul><h3>💡 Final Thoughts</h3><p>Both Git Flow and Feature Branching bring structure to development. The right choice depends on your project’s scale, team size, and release frequency. Visualizing your workflow, like we did here, can make decision-making easier and help your team align on processes.</p><p>Do you use one of these models, or a hybrid of both? Share your thoughts in the comments!</p><p><em>Follow me on Medium for more tech insights, DevOps practices, and Git mastery tips!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c28fb608225b" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>