<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: knox-night</title>
    <description>The latest articles on DEV Community by knox-night (@knoxnight).</description>
    <link>https://dev.to/knoxnight</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4181132%2F95f18243-d33a-47ef-b635-d95e46cb36c9.png</url>
      <title>DEV Community: knox-night</title>
      <link>https://dev.to/knoxnight</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/knoxnight"/>
    <language>en</language>
    <item>
      <title>Drowning in GitHub notifications? I built a fix</title>
      <dc:creator>knox-night</dc:creator>
      <pubDate>Tue, 13 Oct 2026 05:58:29 +0000</pubDate>
      <link>https://dev.to/knoxnight/drowning-in-github-notifications-i-built-a-fix-1gjd</link>
      <guid>https://dev.to/knoxnight/drowning-in-github-notifications-i-built-a-fix-1gjd</guid>
      <description>&lt;p&gt;I built GitHub Digest to fix a problem I kept running into: my GitHub notifications were buried in noise, and I couldn't tell what was actually waiting on me.&lt;/p&gt;

&lt;h2&gt;
  
  
  The problem
&lt;/h2&gt;

&lt;p&gt;My GitHub notifications were a mess. Hundreds of them, and I could never tell which ones were waiting on me and which were just noise. A review request would sit under 40 threads I didn't care about.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I built
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;GitHub Digest&lt;/strong&gt; logs you in with GitHub and sorts your notifications into three groups:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Needs you now:&lt;/strong&gt; review requests, questions aimed at you, failed builds&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Worth a look today:&lt;/strong&gt; mentions and comments&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Can wait:&lt;/strong&gt; everything else&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Each thread also gets:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;A short AI-written summary of what it's asking you to do&lt;/li&gt;
&lt;li&gt;A "Why it's here" line, like "Someone needs your review"&lt;/li&gt;
&lt;li&gt;Done and Mute buttons, so a thread you don't care about stays gone&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Review requests that sit for 2+ days get a "Waiting" badge.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fv06iw1z0v4f4dipvnxjf.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fv06iw1z0v4f4dipvnxjf.png" alt=" " width="799" height="362"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  How it works
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Backend:&lt;/strong&gt; Node.js and Express&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Login:&lt;/strong&gt; GitHub OAuth. It only asks for &lt;code&gt;read:user&lt;/code&gt; and &lt;code&gt;notifications&lt;/code&gt;, never access to your code&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Database:&lt;/strong&gt; Turso (hosted SQLite). Access tokens are encrypted before they're stored&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;AI summaries:&lt;/strong&gt; Google Gemini, for your 20 most urgent threads. Only the title, type, reason and repo name are sent, never the thread contents&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Hosting:&lt;/strong&gt; Render&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  What I learned
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Getting OAuth, sessions and a database working together taught me more than any tutorial.&lt;/li&gt;
&lt;li&gt;A bug that only showed up on the live site (a wrongly named environment variable) took me hours to find. Check your deploy logs first.&lt;/li&gt;
&lt;li&gt;Someone on Reddit told me a priority label is easier to trust when it explains itself. I added the "Why it's here" line the same day.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  What's next
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Letting users correct a priority when it's wrong&lt;/li&gt;
&lt;li&gt;Daily email digests (the code is in, but I haven't turned it on yet)&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;It's free while I build it. Try it here: &lt;a href="https://githubdigest.space" rel="noopener noreferrer"&gt;https://githubdigest.space&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;I'm building this solo and would love honest feedback. What's confusing, what's missing, and what would make you actually use it?&lt;/p&gt;

</description>
      <category>ai</category>
      <category>webdev</category>
      <category>productivity</category>
      <category>github</category>
    </item>
  </channel>
</rss>
