Keeping track of pull request reviews can easily become a productivity sink. You assign reviewers on GitHub and hope they notice — maybe they do, maybe they don’t. Meanwhile Slack channels are full of pings and team chatter, and important review notifications get buried fast. 😩
If you’re like me — jumping between code, Slack, and multiple projects — you want direct, personal alerts that land in your Slack DMs the moment something needs your attention. The good news? GitHub actually supports this natively; it just isn’t super obvious how to enable it.
Here’s how I set it up, step by step, so I never miss a review request again 👇
📬 What This Does
Once configured, GitHub will send real-time Slack alerts straight to your direct messages for activities like:
Someone requests your review
Comments on a PR you're involved in
Pull request updates that matter to you
This means no more:
Scrolling through team channels looking for your name
Reliance on email notifications that arrive late
Manually nudging teammates to review
🛠 Setup: Quick & Practical
Here’s how to get personal Slack notifications working with GitHub’s built-in features:
1. Sign in to GitHub
Open GitHub and go to Settings via your profile icon.
2. Find Scheduled reminders
In the settings sidebar, look for Scheduled reminders. That’s where you’ll configure notifications.
3. Create a New Reminder
Click “Add your first reminder”.
4. Connect Your Slack Workspace
Authorize GitHub to send notifications to Slack. This connects your GitHub account to your Slack workspace.
5. Enable Real-Time Alerts
Check the box for Enable real-time alerts. This ensures you get instant Slack DMs instead of delayed summaries.
6. Choose What Matters
Select the types of notifications you want — e.g., review requests, comments, approvals, etc.
7. Save Your Reminder
Click “Create reminder”, and you’re all set.
Boom — now GitHub will DM you relevant alerts in Slack without adding noise to team channels.
🧠 Why This Is Better Than Other Tools
Sure, there are bots, custom workflows, and third-party services that can forward GitHub events to Slack, but they often:
Spam team channels instead of personal DMs
Require extra setup, maintenance, or costs
Add complexity without much benefit
By using GitHub’s own integrations, the alerts stay personal, reliable, and aligned with exactly what you care about.
💡 Pro Tips
✨ Only Enable What You Need
Too many notifications defeat the purpose. Pick only the ones that help you act faster (e.g., review requests and comments).
📌 Check That Real-Time Box
If you skip enabling real-time alerts, GitHub will only send scheduled reminders — which aren’t as useful when you're trying to respond quickly.
👥 Team Setup Still Matters
If your entire team needs better notifications, use shared repository subscriptions in Slack too, so channels get relevant updates without personal DM clutter.
🧩 Final Thoughts
Setting up personal Slack notifications for GitHub pull request reviews takes minutes, but the payoff is real: faster responses, fewer missed reviews, and communication that actually helps instead of distracts.
If you want to refine this further or integrate it with other workflows — I’d love to help!
Reference
Sponsored
Feeling stuck or preparing for your next iOS role? Check out my 4-week iOS Coaching Program for hands-on guidance to sharpen your technical judgment and career direction.
If you enjoy this newsletter, you can always buy me a coffee — it’s deeply appreciated ☕️