> ## Documentation Index
> Fetch the complete documentation index at: https://docs.gitnotifier.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Notifications

> See which GitHub pull request, review, comment, CI, and release events GitNotifier sends to Slack, including routing behavior and mention rules.

GitNotifier focuses on high-signal pull request activity. Here are the events we react on and \_can \_forward.

## Pull Request Events

* Review requested
* Review request removed
* Assignment / unassignment
* Review submitted (including approved and changes requested)
* PR opened
* PR merged
* PR closed without merge
* New comments on PRs

## Review Comment Routing

For GitHub `pull_request_review_comment` notifications, GitNotifier routes recipients based on whether a comment starts a thread or replies in a thread.

* Top-level human comment: notify the PR audience (author, assignees, requested reviewers), excluding the sender.
* Top-level bot comment: notify nobody.
* Reply in a thread: notify the PR author, non-bot thread participants, and the replied human user (excluding the sender).
* Reply to a bot message: skip the replied-user recipient, but still notify the PR author and non-bot thread participants.
* `@mentions` on human comments/replies notify mapped users in our DB, even if they are not PR author/assignee/reviewer.
* Top-level bot comments are strict no-notify, including mentions.

If **Reviewer Comment Quiet Mode** is enabled for a user, GitNotifier mutes reviewer-scoped PR comment notifications for that user while still delivering direct `@mentions`.

## Team Review Request Mute Behavior

When you mute a GitHub team slug in Slack App Home and a PR is review-requested to that team:

* GitNotifier skips your review-request DM for that event.
* GitNotifier auto-mutes that PR for your future notifications.
* Direct `@mentions` to your GitHub username still notify you.
* If you were also explicitly requested as an individual reviewer, notifications continue as usual.

### Examples

* John posts a top-level review comment -> PR audience is notified.
* Bob replies to John's thread comment -> John, PR author, and other thread participants are notified (deduped, excluding Bob).
* John and Bob each post separate top-level comments -> PR audience is notified for both comments.
* `coderabbit[bot]` posts a top-level comment -> nobody is notified.
* John replies to `coderabbit[bot]` in thread -> PR author and other non-bot thread participants are notified.
* `coderabbit[bot]` replies to John's thread comment -> John, PR author, and other non-bot thread participants are notified.

## CI Signals

* Check suite failures
* Workflow job failures
* Main/default branch failure alerts after merge
* Ready-to-merge signal when CI succeeds

## Release Discussion Mentions

Mentions in GitHub release discussions can be sent to Slack.