Skip to content

Instantly share code, notes, and snippets.

@BPScott
Last active February 7, 2024 16:16
Show Gist options
  • Star 54 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save BPScott/1366790 to your computer and use it in GitHub Desktop.
Save BPScott/1366790 to your computer and use it in GitHub Desktop.
Github suggestion: Per-organization email overrides

This totally happened, y'all can stop +1ing this now. GitHub Blog post. Direct link to settings where you can set this.


#Per-organization / per-repo email overrides - A feature suggestion

Here the concepts "organization" and "user" are interchangeable, I'm talking about an entity that owns a repo, whether it is jQuery or John Resig. I'll stick to using organization as it best represents my original use-case.

##TL;DR

I want to get notifications from my work organization in my work email account, not my personal one. Github should provide an interface for this that isn't "setup forwarding in your personal email".

##The Situation

I use Github for personal projects and as part of a work organization. Currently Github sends all my notifications into a single inbox - my personal one.

##The Problem

I don't want everything to go to my personal email. I want notifications on my work projects to go to my work email and notifications on my personal projects to go to my personal email. Optionally repeat for any other hypothetical organization I might be a member of / user or repo I interact with.

##The Workaround

I can setup forwarding rules in my personal email based off the List-ID header (As told to the masses in this blog post, under "Filter Notifications by Repository or User" but this feels clunky, as though it should be managed as part of Github.

##The Solution

Create an option that allows me to override the email that my notifications should be sent to on a per organization / repo basis.

Github already knows what organization and repo a notification relates to as it sets the List-ID header, changing the from header based off these details that are already exposed should be pretty simple. I already specify the emails addresses I use at https://github.com/account/email. Perhaps an option on there for "receives notifications from: default | organization | organization/repo". Later per-email address notification settings could be added on https://github.com/account/notifications.

##Thoughts?

@ohadlights
Copy link

Amazing

@grokpot
Copy link

grokpot commented May 10, 2019

I believe a large amount of the "+1's" are actually coming from a tangential issue (and why I arrived here):
Per-organization notification preferences.

For example: The problem arises when you have a personal account and a work account. On the personal account, you want to receive emails for every update on the conversations you follow. For example, there's a bug I've been following for a year, and any time someone comments on an issue or PR related to it, I want to be informed.
Now, at work, I'm automatically following every new issue (I can change this, but that's not a great solution). I want to be emailed when I'm mentioned, or a Pull Request Review is requested, but not when someone comments something random. e.g. I'm BE developer and a member of the FE repo, but I only want an email when someone requests a PR from me, not every time a comment on the PR is made.

In essence, the notification preferences should be per-organization. Example:
image
image

@zachleat
Copy link

zachleat commented Feb 6, 2020

Haha this gist helped me find the GitHub setting in the year of our lorde 2020, thank you.

@MeNsaaH
Copy link

MeNsaaH commented Apr 23, 2020

I believe a large amount of the "+1's" are actually coming from a tangential issue (and why I arrived here):
Per-organization notification preferences.

For example: The problem arises when you have a personal account and a work account. On the personal account, you want to receive emails for every update on the conversations you follow. For example, there's a bug I've been following for a year, and any time someone comments on an issue or PR related to it, I want to be informed.
Now, at work, I'm automatically following every new issue (I can change this, but that's not a great solution). I want to be emailed when I'm mentioned, or a Pull Request Review is requested, but not when someone comments something random. e.g. I'm BE developer and a member of the FE repo, but I only want an email when someone requests a PR from me, not every time a comment on the PR is made.

In essence, the notification preferences should be per-organization. Example:
image
image

This is exactly my use case

@SangeetAgarwal
Copy link

https://help.github.com/articles/choosing-the-delivery-method-for-your-notifications/#customizing-email-routes-per-organization
choosing the delivery method for your notifications user documentation

If say a vendor has shared their private repository then how do I ensure that all notifications for that private repository are sent to my work email?
Essentially, all I want to do is setup email notification on a per repository basis.

@asnowfix
Copy link

This does not apply to the repositories I am watching from other orgs: only to those of the orgs I am a member of. I would like to select which email to pick to get notifications for the repos I am watching as an indivual / as an employee / as a contractor.

@erwinpratama
Copy link

+1 for You

@AdamPelc
Copy link

+1

@blaise17
Copy link

blaise17 commented Feb 4, 2022

https://gist.github.com/BPScott/1366790?permalink_comment_id=3266066#gistcomment-3266066
This is exactly what I need too. My work has slack notifications set up for github, so I don't ever need email notifications for that organisation. But for everything else I do want my email notifications.

@masterewot
Copy link

+1 bro

@nickboldt
Copy link

+1, it's annoying that when I make a suggestion on a PR, my non-default personal address is used instead of my work one.

@andersjr1984
Copy link

For anyone still looking for this feature: https://github.com/settings/notifications/custom_routing

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment