Skip to main content
Notifications are the primary mechanism for tracking important activity across repositories and teams. Proper subscription management helps you focus on high-priority updates while reducing noise from low-value events. You can control notification delivery at the repository level using four states: In addition to repository-level settings, you can subscribe to individual conversations—issues, pull requests, or discussions—so you receive updates even when you are not otherwise participating. Use the Subscribe control in the right sidebar of an issue, pull request, or discussion to opt in.
The image displays a screenshot of a pull request on a code repository platform with an option to subscribe for notifications. A "Manual Subscription" button is highlighted at the bottom.
To quickly find every conversation where you have been tagged, use the mentions: search qualifier in the GitHub search bar. For example:
This is a fast way to audit outstanding items that require your attention. You can also route notifications to different delivery destinations depending on your workflow. Manage these options under Settings → Notifications (your account settings). Common delivery destinations include: Use repository-level Custom settings together with per-conversation Subscribe controls to balance broad coverage with low noise. Filter which event types trigger integrations so that only relevant events (for example, failed builds or release tags) are forwarded to external tools.
Tip: Combine repository-level Custom settings and per-conversation Subscriptions to get comprehensive coverage while minimizing interruptions. Route only high-action events (e.g., CI failures, security alerts, or release notes) to external tools like Slack or a monitoring dashboard.
Warning: If you set a repository to Ignoring, all notifications—including @mentions—are suppressed. Use Ignoring only when you are certain you will not miss critical calls to action.
Links and references

Watch Video