-
Notifications
You must be signed in to change notification settings - Fork 9
channel notifications
Jörn Guy Süß edited this page Feb 16, 2026
·
1 revision
This document identifies activities in the global and local workflow diagrams that can be supported by channel notifications (e.g., GitHub notifications, Email, Slack, Teams, webhooks).
The global workflow spans multiple partitions and involves collaboration across roles. The following activities are prime candidates for channel notifications:
| Partition | Activity | Notification Type | Recommended Channels |
|---|---|---|---|
| Repository (GitHub) | Create GitHub Issue or Discussion | New item created | GitHub notifications, Email, Slack/Teams webhooks |
| Repository (GitHub) | Notify contributors (tag team/people, apply labels) | @mention / assignment | GitHub @mentions, Email digests |
| Repository (GitHub) | Collaborative discussion | New comment/reply | GitHub notifications, Email |
| Repository (GitHub) | Issue meets Definition of Ready (DoR) | Status/label change | GitHub label webhooks, Slack bot |
| Development | Create a branch from the issue | Branch created | GitHub webhooks (optional) |
| Development | Push regular, meaningful commits | Commit pushed | GitHub commit notifications (optional, can be noisy) |
| CI / Integration | Run CI checks (build, lint, sushi, IG Publisher) | CI pass/fail | GitHub Actions status, Slack/Email CI bot |
| CI / Integration | CI green & mergeable | Ready for review | GitHub status checks, Slack notification |
| Reviewers / Maintainers | Open Pull Request and request reviewers | PR opened / review requested | GitHub PR notifications, Email |
| Reviewers / Maintainers | Discussion & review comments | New review comment | GitHub notifications |
| Reviewers / Maintainers | PR Approved | Approval granted | GitHub notifications |
| Reviewers / Maintainers | Abandon branch and close PR/issue | Closure notification | GitHub notifications |
| Repository (GitHub) | Squash-merge with clear commit message | PR merged to main | GitHub webhooks, Release notes automation |
- 🔔 Issue/Discussion created → Team awareness
- 🔔 Issue meets Definition of Ready → Signal to start development
- 🔔 CI checks pass/fail → Developer needs immediate feedback
- 🔔 Pull Request opened / reviewers requested → Reviewers need to act
- 🔔 PR approved or changes requested → Author needs to act
- 🔔 PR merged to main → Team awareness, release tracking
- 🔔 PR/Issue closed/abandoned → Stakeholder closure
The local workflow is primarily developer-focused with fewer channel notification opportunities, but some integration points exist:
| Partition | Activity | Notification Type | Recommended Channels |
|---|---|---|---|
| Developer (Editor) | Edit FSH / IG files | Real-time linting feedback | IDE-local only (not channel) |
| Developer (Editor) | Run local validation builds | Build complete | Desktop notification (optional) |
| Developer (Editor) | Build & validation fails | Error summary | Desktop notification |
| Developer (Editor) | Review QA report (output/qa.html) | QA summary | Desktop notification (if automated) |
| Version Control | git add → commit → push | Triggers remote hooks | GitHub notifications, CI/CD pipeline start |
- Most local activities generate immediate, synchronous feedback within the developer's environment
- The push to shared repo is the key transition point that triggers remote channel notifications
- Consider using desktop notifications for long-running local builds if desired
- Enable repository watching for key contributors
- Use @mentions and team mentions strategically
- Configure CODEOWNERS for automatic review requests
- Use GitHub App for Slack/Teams to route notifications
- Configure filters to reduce noise (e.g., only CI failures, PR events)
- Create dedicated channels for specific projects
- GitHub provides email notifications for watched repositories
- Configure digest mode to reduce volume
- GitHub Actions can post status to Slack/Teams
- Configure notifications for failures only to reduce noise
The following symbols are used in the updated process diagrams to indicate notification opportunities:
| Symbol | Meaning |
|---|---|
| 🔔 | Activity that can trigger a channel notification |
| Yellow/highlighted notes | Notification-enabled activities |
See the updated global_process.puml and local_process.puml files for visual indicators.
🦶🦶🦶🦶 This footer is almost everywhere 🦶🦶🦶🦶