<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet type="text/xsl" href="../assets/xml/rss.xsl" media="all"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>A Tiro's Blog (Posts about github)</title><link>https://tiro.org.uk/</link><description></description><atom:link href="https://tiro.org.uk/blog/categories/github.xml" rel="self" type="application/rss+xml"></atom:link><language>en</language><lastBuildDate>Sat, 04 Apr 2026 15:49:49 GMT</lastBuildDate><generator>Nikola (getnikola.com)</generator><docs>http://blogs.law.harvard.edu/tech/rss</docs><item><title>Keeping Dependabot Happy</title><link>https://tiro.org.uk/blog/posts/2026/04/keeping-dependabot-happy/</link><dc:creator>Richard Palmer</dc:creator><description>&lt;p&gt;I found this post from &lt;a class="reference external" href="https://words.filippo.io/dependabot/"&gt;Filippo Valsorda&lt;/a&gt; interesting as it's
increasingly seemed like what was originally something useful (finding out about security alerts
for dependencies) has become a beast that must be fed everyday. The satisfaction of closing a few
Dependabot PRs is swiftly followed by deflation as 2-3x that many new PRs are created the next day. One
thing that would make it much more useful (and I'm baffled as to why it's not done by GitHub) is to have
a clearer UI that splits out PRs into those from developers, security PRs (important!) and then the endless
dependency update ones that can be considered as and when. Instead if you don't keep merging them, you
end up with a open PR count in the hundreds and a feeling that you are not maintaining things.&lt;/p&gt;</description><category>dependabot</category><category>github</category><category>maintainance</category><category>software</category><guid>https://tiro.org.uk/blog/posts/2026/04/keeping-dependabot-happy/</guid><pubDate>Sat, 04 Apr 2026 15:39:20 GMT</pubDate></item></channel></rss>