* TOC

{:toc}

GitHub Notifications are powered by[watched repositories](/v3/activity/watching/).

Users receive notifications for discussions in repositories they watch

Users receive notifications for conversations in repositories they watch

including:

* Issues and their comments

* Pull Requests and their comments

* Comments on any commits

Notifications are also sent fordiscussions in unwatched repositories when the

Notifications are also sent forconversations in unwatched repositories when the

user is involved including:

Reason Name | Description

------------|------------

`subscribed` | The notification arrived because you're watching the repository

`manual` | The notification arrived because you've specifically decided towatchtheitem (via an Issue or Pull Request)

`author` | The notification arrived because you've created theitem

`comment` | The notification arrived because you've commented on theitem

`mention` | The notification arrived because you were specifically**@mentioned** in the content

`team_mention` | The notification arrived because you were on a team that was mentioned (like@org/team)

`state_change` | The notification arrived because you changed theitem state (like closing an Issue or merging a Pull Request)

`assign` | The notification arrived because you were assigned to the Issue

`manual` | The notification arrived because you've specifically decided tosubscribe tothethread (via an Issue or Pull Request)

`author` | The notification arrived because you've created thethread

`comment` | The notification arrived because you've commented on thethread

`mention` | The notification arrived because you were specifically**@mentioned** in the content

`team_mention` | The notification arrived because you were on a team that was mentioned (like@org/team)

`state_change` | The notification arrived because you changed thethread state (like closing an Issue or merging a Pull Request)

`assign` | The notification arrived because you were assigned to the Issue

Note that the`reason` is modified on a per-thread basis, and can change, if the

`reason` on a later notification is different.

`reason` on a later notification is different.

For example, if you are the author of an issue, subsequent notifications on that

issue will have a`reason` of`author`. If you're then**@mentioned** on the same

issue, the notifications you fetch thereafter will have a`reason` of`mention`.

For example, if you are the author of an issue, subsequent notifications on that

issue will have a`reason` of`author`. If you're then**@mentioned** on the same

issue, the notifications you fetch thereafter will have a`reason` of`mention`.

The`reason` remains as`mention`, regardless of whether you're ever mentioned again.

Name | Type | Description

Name | Type | Description

-----|------|--------------

`last_read_at`|`string` | Describes the last point that notifications were checked. Anything updated since this time will not be updated. This is a timestamp in ISO 8601 format:`YYYY-MM-DDTHH:MM:SSZ`. Default:`Time.now`

This checks to see if the current user is subscribed to a thread. You can also

[get a Repository subscription](/v3/activity/watching/#get-a-repository-subscription).

{{#tip}}

Note that subscriptions are only generated if a user is participating in a conversation--for example, they've replied to the thread, were**@mention**ed, or manually subscribe to a thread.

{{/tip}}

This lets you subscribe to a thread, or ignore it. Subscribing to a thread

is unnecessary if the user is already subscribed to the repository. Ignoring

a thread will mute all future notifications (until you comment or get

@mentioned).

This lets you subscribe or unsubscribe from a conversation. Unsubscribing from a conversation mutes all future notifications (until you comment or get**@mention**ed once more).

<%= headers 204 %>