`invalid` | This means the formatting of a field is invalid. The documentation for that resource should be able to give you more specific information.

`already_exists` | This means another resource has the same value as this field. This can happen in resources that must have some unique key (such as Label names).

If resources havecustom validation errors, theywillbe documented withtheresource.

Resources may also sendcustom validation errors (where`code` is`custom`). Custom errorswillalways have a`message` field describingtheerror, as well as a`documentation_url` field pointing to some content that might help you resolve the error.

To prevent abuse, additional rate limits apply to some endpoints that

create content. This rate limit applies to the creation of new content

create content. This rate limit applies to the creation of new content

over a period of time. These rate limits do not apply to private repositories

or GitHub Enterprise installations.

* 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 %>

`subscribed`|`boolean`| Determines if notifications should be received from this repository.

`ignored`|`boolean`| Determines if all notifications should be blocked from this repository.

{{#tip}}

If you would like to watch a repository, set`subscribed` to`true`. If you would like to ignore notifications made within a repository, set`ignored` to`true`. If you would like to stop watching a repository,[delete the repository's subscription](#delete-a-repository-subscription) completely.

{{/tip}}

{{#tip}}

This endpoint should only be used to stop watching a repository. To control whether or not you wish to receive notifications from a repository,[set the repository's subscription manually](#set-a-repository-subscription).

{{/tip}}

<%= headers 405 %>

<%= json\

:sha => nil,

:merged => false,

:message => 'Failure reason'

:message => "Pull Request is not mergeable",

:documentation_url => "https://developer.github.com/v3/pulls/#merge-a-pull-request-merge-button"

%>

TEAM ||={