<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Productivity on Learn, Converse, Share</title><link>http://jmeridth.com/tags/productivity/</link><description>Recent content in Productivity on Learn, Converse, Share</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 16 Jul 2026 00:00:00 -0500</lastBuildDate><atom:link href="http://jmeridth.com/tags/productivity/index.xml" rel="self" type="application/rss+xml"/><item><title>Managing GitHub Notifications</title><link>http://jmeridth.com/posts/managing-github-notifications/</link><pubDate>Thu, 16 Jul 2026 00:00:00 -0500</pubDate><guid>http://jmeridth.com/posts/managing-github-notifications/</guid><description>&lt;p&gt;TL;DR: Centralize all your GitHub notifications into Slack so you stop drowning in email.&lt;/p&gt;
&lt;h2 id="the-problem"&gt;
 The Problem
 &lt;a class="heading-link" href="#the-problem"&gt;
 &lt;i class="fa-solid fa-link" aria-hidden="true" title="Link to heading"&gt;&lt;/i&gt;
 &lt;span class="sr-only"&gt;Link to heading&lt;/span&gt;
 &lt;/a&gt;
&lt;/h2&gt;
&lt;p&gt;If you work across a lot of repositories, GitHub notifications get out of hand fast. Every issue, pull request, review request, mention, CI run, and release wants your attention, and by default much of it lands in your email inbox. Email is where notifications go to die. It is easy to end up with thousands of unread messages and no real signal.&lt;/p&gt;</description></item></channel></rss>