Feature request: Custom routing for forks, or at least individual repositories

[svenssonaxel]

Custom routing allows selecting, for each organization that you are a member of, what email address to use for notifications. However, forks of private repositories count as owned by yourself, so notifications are sent to the default email. This is perhaps by design, but it is not what I would expect.

Feature request: The table for custom routing of notifications should probably have at least these columns:

• The repository in question. This is the most important one, since it can be used as a workaround.
• Forked-from-repository-in-organization.
• Belongs-to-organization: Like now, except not limited to the organizations you're a member of (see Notification custom routing should be applicable for all orgs #32726).
• Notification-coming-from-repository and Notification-coming-from-organization (see Custom Routing Should Work For Outgoing Changes From An Organization #30544).