-
Notifications
You must be signed in to change notification settings - Fork 564
GitHub Notifications
GitHub provides a variety of ways to control what information you receive from repository activities. There is substantial documentation on GitHub.com. For example, these two articles are good references:
- https://help.github.com/articles/about-notifications
- https://help.github.com/articles/managing-notifications
You can control your own notification setting here: https://github.com/settings/notifications
GitHub.com delivers a portion of its email messages via a third-party service. If a GitHub notification is bounced when sent from this service, your email address will be flagged and subsequent messages will not be sent. This may happen if your email system stops responding for a while.
If you suspect that you are not receiving all notifications:
- Go to https://github.com/notifications (or https://github.com/notifications/participating) and check if there are notification listed that are not in your email.
- If you are missing some notifications, go to https://github.com/contact and submit a request to have your account unflagged. In your message, give a pointer to a notification that is visible on GitHub.com but was not sent to your email address.
Issues can also be monitored directly from a browser from the Notifications page, where you can see a summary of updates. You can stop receiving notifications for any issue by unsubscribing from it by clicking the volume sound symbol (similar to 🔊).
There are a number of browser extensions that show browser and/or desktop alerts when there are updates to issues that you are monitoring.
- Notifier for Github: https://github.com/sindresorhus/notifier-for-github
- Advanced Github Notifier: https://github.com/freaktechnik/advanced-github-notifier
Copyright © Trilinos a Series of LF Projects, LLC
For web site terms of use, trademark policy and other project policies please see https://lfprojects.org.
Trilinos Developer Home
Trilinos Package Owners
Policies
New Developers
Trilinos PR/CR
Productivity++
Support Policy
Test Dashboard Policy
Testing Policy
Managing Issues
New Issue Quick Ref
Handling Stale Issues and Pull Requests
Release Notes
Software Quality Plan
Proposing a New Package
Guidance on Copyrights and Licenses
Tools
CMake
Doxygen
git
GitHub Notifications
Mail lists
Clang-format
Version Control
Initial git setup
'feature'/'develop'/'master' (cheatsheet)
Simple centralized workflow
Building
SEMS Dev Env
Mac OS X
ATDM Platforms
Containers
Development Tips
Automated Workflows
Testing
Test Harness
Pull Request Testing
Submitting a Pull Request
Pull Request Workflow
Reproducing PR Errors
Addressing Test Failures
Trilinos Status Table Archive
Pre-push (Checkin) Testing
Remote pull/test/push
PR Creation & Approval Guidelines for Tpetra, Ifpack2, and MueLu Developers