<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Repo Automation on Sagar Panda | DevOps &amp; Cloud Infra Engineer</title><link>https://new.sagarpanda.com/tags/repo-automation/</link><description>Recent content in Repo Automation on Sagar Panda | DevOps &amp; Cloud Infra Engineer</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sun, 24 May 2026 12:45:10 +0530</lastBuildDate><atom:link href="https://new.sagarpanda.com/tags/repo-automation/index.xml" rel="self" type="application/rss+xml"/><item><title>Turn Your GitHub Repository into a Self-Managing Workflow</title><link>https://new.sagarpanda.com/blogs/github-automation/</link><pubDate>Sun, 24 May 2026 12:45:10 +0530</pubDate><guid>https://new.sagarpanda.com/blogs/github-automation/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;a href="#introduction" class="heading-anchor" aria-label="Link to this section"&gt;&lt;svg class="h-4 w-4" aria-hidden="true" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"&gt;&lt;g fill="none" stroke="currentColor" stroke-linecap="round" stroke-linejoin="round" stroke-width="2"&gt;&lt;path d="M10 13a5 5 0 0 0 7.54.54l3-3a5 5 0 0 0-7.07-7.07l-1.72 1.71"/&gt;&lt;path d="M14 11a5 5 0 0 0-7.54-.54l-3 3a5 5 0 0 0 7.07 7.07l1.71-1.71"/&gt;&lt;/g&gt;&lt;/svg&gt;&lt;/a&gt;&lt;/h2&gt;&lt;p&gt;&lt;a
 href="https://new.sagarpanda.com/blogs/github-actions/"&gt;In my previous article, I wrote the fundamentals of GitHub Actions and how they can simplify CI/CD pipelines&lt;/a&gt;. But modern repositories need much more than just automated builds and deployments.&lt;/p&gt;
&lt;p&gt;As projects grow, maintaining pull requests, managing issues, handling releases, updating dependencies, and reviewing security manually becomes repetitive and time-consuming.&lt;/p&gt;</description></item></channel></rss>