From dc69f7ab95466c43ef5be62f5f068d3f377104f2 Mon Sep 17 00:00:00 2001 From: woksin Date: Thu, 6 Aug 2026 11:04:21 +0200 Subject: [PATCH] Document how to set up GitHub notifications Contributors had no way to discover that watching every repository in the organization is something they should do, or that email delivery has to be enabled by hand because GitHub exposes no API for it. Point at the recipe in the Automation repository from the guide people actually read first. Co-Authored-By: Claude Opus 5 (1M context) Claude-Session: https://claude.ai/code/session_01C9jRGdARCHoKhKfUmrA3wV --- contributing.md | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) diff --git a/contributing.md b/contributing.md index fd229c7..92d0e9a 100644 --- a/contributing.md +++ b/contributing.md @@ -9,6 +9,26 @@ The following specific topics are important: * [Standardization](./standardization.md) * [C#](csharp.md) +## Notifications + +GitHub only notifies you about repositories you explicitly **watch**, and new repositories appear in the +organization regularly, so your subscriptions drift out of date on their own. Reconcile them in one command: + +```bash +git clone git@github.com:Cratis/Automation.git +cd Automation/Source/GitHub +./gh-subscribe.sh +``` + +It watches every repository in the organization, mutes archived repositories and forks, and follows organization +members. It is idempotent, so run it again whenever new repositories show up. You do not have to be an organization +member — non-members get the public repositories and public member list. + +Turning on **email** delivery is a separate manual step. GitHub exposes no API for delivery preferences, so watching +everything still only fills the web inbox until you tick the Email boxes under +[notification settings](https://github.com/settings/notifications). The full recipe, including that step, is in the +[notifications guide in the Automation repository](https://github.com/Cratis/Automation/blob/main/Documentation/GitHub/notifications.md). + ## Size Contributions, be it features or bug fixes should be small and digestible.