| 1 | --- |
| 2 | title: Notifications |
| 3 | description: What needs you, and what you follow, as it happens. One thread per issue, pull request, workflow or deployment, with why you were told. Choose what you hear of with subscriptions, watching and email settings. |
| 4 | --- |
| 5 | |
| 6 | **Notifications** tell you when something needs you, or when something |
| 7 | happens to work you answer for or follow: an agent is waiting on you, |
| 8 | someone asked you to review a pull request, checks failed on your pull |
| 9 | request, a deployment failed, someone mentioned you. You are never told |
| 10 | about what you did yourself. |
| 11 | |
| 12 | Open them from the bell in the top bar, or from the bottom bar on a |
| 13 | phone. The number on it is what is unread. The bell at the right of the |
| 14 | page's header opens the same notifications in a panel beside the page; its |
| 15 | number is amber while something is waiting on you, red while a failure is |
| 16 | unread, and lavender otherwise. |
| 17 | |
| 18 | ## Threads |
| 19 | |
| 20 | Notifications hold one **thread** for each thing you were told about: |
| 21 | |
| 22 | - an issue |
| 23 | - a pull request |
| 24 | - a workflow on one branch |
| 25 | - a deployment: a project's production, or one pull request's preview |
| 26 | - a workflow run waiting for your review to deploy to an environment |
| 27 | - a repository's security alerts of one kind: its secrets, its code |
| 28 | scanning alerts, or its vulnerable dependencies (see [Security](#security)) |
| 29 | - your security digest for a workspace |
| 30 | |
| 31 | When something new happens on a thread, it comes back to the top of your |
| 32 | notifications, unread, even if you had marked it done. It is not added a second |
| 33 | time. A thread that is snoozed stays snoozed until its time. |
| 34 | |
| 35 | Each card shows the latest activity's title, why you were told (see |
| 36 | [reasons](#reasons)), and, when more than one thing has happened, how many, |
| 37 | such as **3 updates**. g1t keeps the last 10 activities of each thread. |
| 38 | |
| 39 | While a thread is unread it keeps the most urgent of what happened since |
| 40 | you last read it. A failure followed by a comment still shows as a failure |
| 41 | until you read it. |
| 42 | |
| 43 | ## Reasons |
| 44 | |
| 45 | Every thread says why you were told of its latest activity. When you are |
| 46 | told of one thing for more than one reason, the first that applies in this |
| 47 | table is shown. |
| 48 | |
| 49 | | Reason | Shown as | Why you were told | |
| 50 | | --- | --- | --- | |
| 51 | | `agent` | agent waiting | An agent is waiting on you: it asked a question, or it stopped until a person steps in. | |
| 52 | | `review_requested` | review requested | Someone asked you, or a team you are in, to review a pull request; it changes files you own; or you are one of its reviewers. Also a workflow run waiting for you, as one of an [environment's reviewers](/guides/actions/#environments), to approve its deployment, and, for a workspace's owners, a member's token made for the workspace waiting for [approval](/guides/authentication/#a-workspaces-rules-for-tokens) (in Notifications only, never emailed). | |
| 53 | | `assign` | assigned | You were assigned, or you are an assignee. | |
| 54 | | `mention` | mentioned | Someone mentioned you with `@username`, or you were mentioned on it before. | |
| 55 | | `team_mention` | team mentioned | Someone mentioned a [team](/guides/teams/#mentions) you are in with `@workspace/team`, or a team you are in was mentioned on it before. | |
| 56 | | `ci_activity` | CI activity | A check, workflow or deployment on your work finished badly, or recovered. | |
| 57 | | `security_alert` | security alert | A scan found new secrets, code scanning alerts or vulnerable dependencies on a repository you look after (one thread per repository and kind; see [Security](#security)), a push of yours that push protection refused, a [vulnerability report](/guides/security/advisories/#private-vulnerability-reporting) sent to a repository you look after, a [bypass request](/guides/security/secret-protection/#delegated-bypass) to review or its answer, or your security digest. The workspace's owners and security managers hear of these; watchers who chose **Security alerts** do too, if they can see findings. | |
| 58 | | `state_change` | state changed | It was closed, reopened or merged. | |
| 59 | | `author` | your work | You opened it, or you asked g1t for it. Also an owner's answer to your [token made for a workspace](/guides/authentication/#create-a-token) waiting for approval, or its revocation. | |
| 60 | | `comment` | commented | You commented on it. | |
| 61 | | `manual` | subscribed | You subscribed to it yourself. | |
| 62 | | `subscribed` | watching | You watch its repository. | |
| 63 | |
| 64 | ## What lands there |
| 65 | |
| 66 | Each item comes from something that happened on g1t. Who is told depends on |
| 67 | what it was: |
| 68 | |
| 69 | | What happened | Who is told | Reason | Shown as | |
| 70 | | --- | --- | --- | --- | |
| 71 | | An agent asked a question of the agent on a pull request, or handed it work | The person the pull request belongs to, and its issue's author and assignees | `agent` | Needs you | |
| 72 | | g1t stopped on a pull request until a person steps in | The same people | `agent` | Needs you | |
| 73 | | Someone asked for reviews on a pull request, or opened one with reviewers | The reviewers asked | `review_requested` | Needs you | |
| 74 | | Someone asked a team to review a pull request | Everyone in the team and its child teams, or, with [review assignment](/guides/teams/#review-assignment), the people picked | `review_requested` | Needs you | |
| 75 | | A workflow run's jobs wait for an [environment's reviewers](/guides/actions/#environments) | Each reviewer, and everyone in a reviewing team ("Deploy is waiting for your review to deploy to production in acme/api"), but not whoever started the run when it may not approve it | `review_requested` | Needs you | |
| 76 | | A pull request changes files a [CODEOWNERS file](/guides/codeowners/) gives you or your team | The owners asked: "acme/api#42 changes files you own" | `review_requested` | Needs you | |
| 77 | | Someone assigned people to an issue or pull request, or opened one with assignees | The people newly assigned | `assign` | Info | |
| 78 | | Checks failed, or could not run, on a pull request | The person the pull request belongs to | `ci_activity` | Error | |
| 79 | | A workflow failed on a pull request | The person the pull request belongs to | `ci_activity` | Error | |
| 80 | | A workflow failed on a branch | Whoever pushed the commit it ran on | `ci_activity` | Error | |
| 81 | | A preview of a pull request failed to deploy | The person the pull request belongs to, and people watching deployments | `ci_activity`, or `subscribed` for watchers | Error | |
| 82 | | Production failed to deploy | Whoever pushed or started it, and people watching deployments | `ci_activity`, or `subscribed` for watchers | Error | |
| 83 | | A deployment went live | People watching deployments; after a failure, also whoever was told of the failure | `ci_activity`, or `subscribed` for watchers | Success | |
| 84 | | g1t finished a change and marked it ready for review | The person who asked g1t for it | `author` | Success | |
| 85 | | g1t reviewed a pull request | The person the pull request belongs to | `author` | Success when approved, Info when it asks for changes | |
| 86 | | A pull request was merged | Everyone subscribed to it, and people watching pull requests | `state_change`, or `subscribed` for watchers | Success | |
| 87 | | An issue or pull request was closed, or an issue was reopened | Everyone subscribed to it, and people watching its kind | `state_change`, or `subscribed` for watchers | Info | |
| 88 | | Someone mentioned you with `@username` in a comment | You | `mention` | Info | |
| 89 | | Someone mentioned a team with `@workspace/team` in a comment, or in an issue or pull request they opened | Everyone in the team and its child teams, when the team's notifications are on and the writer can see the team | `team_mention` | Info | |
| 90 | | Someone commented on an issue or pull request | Everyone subscribed to it, and people watching its kind | Why each is subscribed, or `subscribed` for watchers | Info, or Success for an approval | |
| 91 | | One of your workspace's agents commented on or reviewed an issue or pull request, as itself | The same people, and the person the pull request belongs to for a review; shown as from "Margo (agent)", with "(advisory)" on a review. See [agent reviews](/guides/pull-requests/#agent-reviews) | Why each is subscribed, or `author` for a review | Info, or Success for an approval | |
| 92 | | An issue or pull request was opened | People watching its kind | `subscribed` | Info | |
| 93 | |
| 94 | "The person a pull request belongs to" is its author, or, for a change g1t |
| 95 | made, the person who asked for it. An approval or a request for changes |
| 96 | always reaches that person. g1t itself is never told. A mention in code or |
| 97 | in a quoted line does not count. |
| 98 | |
| 99 | Some threads close themselves once they no longer need you: |
| 100 | |
| 101 | - When an agent was waiting on you, the thread moves to Done as soon as the |
| 102 | agent picks back up: it resumes, its pull request changes, a merge is |
| 103 | asked for, or the pull request is merged or closed. |
| 104 | - When a review request to you is removed, that thread moves to Done. |
| 105 | |
| 106 | New activity brings either back, as with any thread. |
| 107 | |
| 108 | You only see items about repositories you can read. If you lose access to a |
| 109 | repository, its items leave your notifications the next time you open them. |
| 110 | |
| 111 | ## Subscriptions |
| 112 | |
| 113 | You are **subscribed** to an issue or pull request, and hear of what |
| 114 | happens on it, without doing anything when you: |
| 115 | |
| 116 | - opened it, or asked g1t for it |
| 117 | - are assigned to it |
| 118 | - are one of its reviewers |
| 119 | - commented on it |
| 120 | - were mentioned in it, by name or through a team |
| 121 | |
| 122 | You can also subscribe to any issue or pull request yourself, or |
| 123 | unsubscribe from one. |
| 124 | |
| 125 | | You are | You hear of | |
| 126 | | --- | --- | |
| 127 | | Subscribed | Everything in [What lands there](#what-lands-there) that goes to everyone subscribed: comments, closes, reopens and merges. | |
| 128 | | Unsubscribed | Only what is asked of you or is about your own work: an agent waiting on you, a review request, an assignment, a mention of you or your team, and failed checks, workflows and deployments. Commenting on it, or being mentioned in it, subscribes you again. | |
| 129 | | Ignoring it | Nothing on it at all, not even a mention. Only you can undo this. | |
| 130 | |
| 131 | To subscribe to an issue or pull request, or unsubscribe: |
| 132 | |
| 133 | 1. Open the issue or pull request. |
| 134 | 2. In the sidebar, under **Notifications**, select **Subscribe** or |
| 135 | **Unsubscribe**. |
| 136 | |
| 137 | The line under the button says where you stand, such as "You're subscribed |
| 138 | because you were assigned.", "You're not subscribed. You'll still hear if |
| 139 | you're mentioned or asked to review." or "You ignore this thread." |
| 140 | |
| 141 | To ignore an issue or pull request, use the API: |
| 142 | `PUT /repos/{owner}/{name}/issues/{number}/subscription` with |
| 143 | `"ignored": true`, or the `notifications` tool's `subscribe` action with |
| 144 | `ignored`. See [from the API and agents](#from-the-api-and-agents). While |
| 145 | you ignore one, its button reads **Stop ignoring**, which puts you back to |
| 146 | the default: subscribed only while you take part. |
| 147 | |
| 148 | ## Watching a repository |
| 149 | |
| 150 | How you **watch** a repository decides what you hear of on it beyond what |
| 151 | you take part in. |
| 152 | |
| 153 | | Level | You hear of | |
| 154 | | --- | --- | |
| 155 | | **Participating and @mentions** | Only what you take part in or are mentioned in. The default. | |
| 156 | | **All activity** | Also every issue and pull request opened, commented on, closed, reopened or merged, and every deployment. | |
| 157 | | **Ignore** | Nothing on the repository at all, not even a mention or a review request. | |
| 158 | | **Custom** | What you take part in, and the kinds you choose: **Issues**, **Pull requests**, **Deployments** and **Security alerts**. Security alerts reach only those with Write on the repository, who can see its findings. | |
| 159 | |
| 160 | To change how you watch a repository: |
| 161 | |
| 162 | 1. Open the repository. |
| 163 | 2. In the header, open the **Watch** menu. |
| 164 | 3. Select a level. For **Custom**, tick the kinds you want. Unticking |
| 165 | every kind puts you back on **Participating and @mentions**. |
| 166 | |
| 167 | A repository you create is watched the way you choose in |
| 168 | [your settings](#settings): **All activity** unless you change it. |
| 169 | |
| 170 | ## Pages that update live |
| 171 | |
| 172 | A repository's pages keep up with it while you are on them, without a |
| 173 | reload and whatever you watch: new commits, pull requests, checks, runs |
| 174 | and comments appear as they happen. |
| 175 | |
| 176 | | Page | Updates when | |
| 177 | | --- | --- | |
| 178 | | **Overview** and **Files** | A branch or tag is pushed, created or deleted, a check or run reports on a commit, a release is published, or a deployment moves. | |
| 179 | | **Commits** | Commits are pushed to the branch. They wait under a **3 new commits · Show** bar at the top instead of moving the list while you read; checks on the commits shown update in place. | |
| 180 | | **Branches** | A branch is pushed, created, renamed or deleted. | |
| 181 | | **Tags** | A tag is pushed or deleted, or a release is published. | |
| 182 | | **Pull requests** and **Issues** | One is opened, updated, reviewed, commented on, checked, merged or closed. | |
| 183 | | A **pull request** | Commits are pushed to it, its checks report, someone reviews or comments, or it is merged or closed. New items join its timeline where you are reading; if you are at the end of the page, it follows them down. | |
| 184 | | An **issue** | Someone comments on it or changes it, or a pull request linked to it moves. | |
| 185 | | **Actions** and a **run** | A run starts, one of its jobs starts or finishes, or the run finishes. A running job's log streams on its own. | |
| 186 | | **Security** | An alert is opened, fixed, dismissed or reopened. | |
| 187 | |
| 188 | A page refreshes a second after the last change it shows, so a burst of |
| 189 | them is one refresh. It never refreshes while you are typing in it or have |
| 190 | a dialog open: the change waits until you leave the field or close the |
| 191 | dialog. A tab you are not looking at refreshes at most once a minute, and |
| 192 | as soon as you come back to it. |
| 193 | |
| 194 | How it works: each signed-in tab keeps one live connection to g1t (the |
| 195 | same one that brings notifications and chat counts). Opening a |
| 196 | repository's page asks to follow that repository, and g1t first checks you |
| 197 | can read it. From then on, every push, pull request, issue, comment, |
| 198 | review, check, run, release and security alert there sends that tab a |
| 199 | short note naming only what kind of thing changed and where: a branch, a |
| 200 | number, a commit. Never a title, a message or code. The page then reads |
| 201 | itself again, with your access as it is now. Following lasts fifteen |
| 202 | minutes and is renewed while the page stays open, so someone who loses |
| 203 | access stops hearing of the repository within that time. |
| 204 | |
| 205 | Signed out, on a public repository, or while the live connection is down, |
| 206 | pages fall back to checking for themselves: when you come back to the tab |
| 207 | (at most every 30 seconds), and once a minute while it is in view. |
| 208 | |
| 209 | ## Security |
| 210 | |
| 211 | Security alerts are told the way they can be lived with. A scan that finds |
| 212 | forty vulnerabilities is one notification, not forty: each repository has |
| 213 | one thread per kind of alert (secrets, code scanning alerts, vulnerable |
| 214 | dependencies), titled by what the latest scan found, "3 new vulnerabilities |
| 215 | in acme/rocket: 1 critical, 2 high", with the worst new alert as its line. |
| 216 | The next scan brings the same thread back up to date rather than adding |
| 217 | another; a scan that only fixed or dismissed alerts refreshes it quietly, |
| 218 | "2 open vulnerabilities in acme/rocket: 2 high" with "1 fixed" in its |
| 219 | history, without waking you, and marks it done when nothing is left open. |
| 220 | |
| 221 | What reaches you, and when, follows the alert's severity: |
| 222 | |
| 223 | | Alert | Who | When | |
| 224 | | --- | --- | --- | |
| 225 | | Critical or high | The workspace's owners and security managers, and watchers who chose **Security alerts**. | At once, as an error, with a pop-up like a mention's. | |
| 226 | | A push of yours that push protection refused | You. | At once, whatever you chose. | |
| 227 | | A vulnerability report, a bypass request | The owners and security managers; the reviewers. | At once, as something waiting on you. | |
| 228 | | Medium or low | The same people. | In your **security digest**, once a day or once a week as you choose, or at once, or never. | |
| 229 | | A published advisory | Watchers who chose **Security alerts**. | At once, as information. | |
| 230 | |
| 231 | The **security digest** is one notification and one email per workspace, |
| 232 | "Security digest for acme: 4 new medium vulnerabilities in 2 repositories, |
| 233 | 1 new low secret in 1 repository", naming the newest alerts, sent in the |
| 234 | morning (UTC): every day, or on Mondays. Owners and security managers get |
| 235 | the urgent alerts whatever their settings say; those alerts are theirs to |
| 236 | act on. Everyone else can turn the urgent ones off too, and anyone can |
| 237 | choose how the rest arrive, in [Settings](#settings). |
| 238 | |
| 239 | Fixes and dismissals never make a notification of their own. The findings |
| 240 | themselves are always on each repository's [Security page](/guides/security/). |
| 241 | |
| 242 | ## Email |
| 243 | |
| 244 | You can also be emailed when you are told of something. By default, g1t |
| 245 | emails you for four reasons: **agent waiting**, **review requested**, |
| 246 | **mentioned** and **security alert**. Each time you are told of something |
| 247 | for a reason you chose, g1t sends one email with what happened and a link |
| 248 | to it; a security digest is one email. |
| 249 | |
| 250 | An email is sent only when: |
| 251 | |
| 252 | - your account's email address is confirmed, and |
| 253 | - you can still read the repository it is about. |
| 254 | |
| 255 | The foot of each email says why you got it, and links to |
| 256 | [g1t.sh/settings/notifications](https://g1t.sh/settings/notifications). |
| 257 | |
| 258 | ## On your phone |
| 259 | |
| 260 | [The phone app](/guides/mobile/) gets the same notifications as |
| 261 | [browser notifications](/guides/chat/#notifications), under the same |
| 262 | rules: |
| 263 | |
| 264 | - only what you chose under **Notify me about**, for each workspace; |
| 265 | - never while **Do not disturb** is on; |
| 266 | - nothing from a conversation you [muted](/guides/chat/#star-and-mute), |
| 267 | but a direct message or a mention of you; |
| 268 | - nothing while a g1t tab, or the app itself, is in front of you: it tells you there. |
| 269 | |
| 270 | Your phone is registered when you allow notifications in the app. |
| 271 | **Send a test notification**, here or in the app under **More**, reaches it too. Signing out of the app stops |
| 272 | them on that phone. g1t pushes to your 10 most recent phones, and stops |
| 273 | on its own for a phone the app was removed from. Phones are reached |
| 274 | through Expo's push service, which hands each notification to Google |
| 275 | (Android) or Apple (iOS); a [self-hosted g1t](/guides/self-hosting/#the-phone-app) |
| 276 | can turn that off. |
| 277 | |
| 278 | ## Settings |
| 279 | |
| 280 | **Settings → Notifications**, at |
| 281 | [g1t.sh/settings/notifications](https://g1t.sh/settings/notifications), |
| 282 | holds your choices: |
| 283 | |
| 284 | | Setting | What it does | Default | |
| 285 | | --- | --- | --- | |
| 286 | | **Sounds**, **Sound set**, **Volume**, one switch per sound | What chat sounds like; see [Sounds and do not disturb](/guides/chat/#sounds-and-do-not-disturb). | On, Soft, 60, all but Sent | |
| 287 | | **Do not disturb** | Silences sounds, pop-ups, and browser and phone notifications until a time you choose. | Off | |
| 288 | | **Desktop notifications** | A system notification from an open tab for a message to you while the window is behind another. In [the desktop app](/guides/desktop/) it is on, and the app shows them itself. | Off | |
| 289 | | **Notify me about**, **Browser notifications** | What pops up and is pushed; see [chat notifications](/guides/chat/#notifications). | DMs and mentions; off | |
| 290 | | **Email** | One checkbox per reason: you are also emailed when you are told of something for it. | agent waiting, review requested, mentioned, security alert | |
| 291 | | **Security: Critical and high alerts at once** | Whether urgent alerts on repositories you watch for security reach you at once. The workspaces you own or manage security for tell you whatever this says. | On | |
| 292 | | **Security: Medium and low alerts** | In a daily digest, in a weekly digest, at once, or not at all. | Daily digest | |
| 293 | | **Repositories you create** | How you watch a new repository you create: **Participating and @mentions** or **All activity**. | All activity | |
| 294 | | **Watched repositories** | Every repository you watch other than the default way, with how. | | |
| 295 | |
| 296 | ## Tabs |
| 297 | |
| 298 | | Tab | Shows | |
| 299 | | --- | --- | |
| 300 | | **All** | Everything, with what is waiting on you first | |
| 301 | | **Needs you** | What is waiting on you: an agent, or a review asked of you | |
| 302 | | **Errors** | Failed checks, workflows and deployments | |
| 303 | | **Success** | Merges, approvals, finished agent work, and deployments that went live | |
| 304 | | **Info** | Mentions, comments, assignments, and what you watch | |
| 305 | |
| 306 | The count beside each tab is what is unread under it. |
| 307 | |
| 308 | ## The Notifications page |
| 309 | |
| 310 | The bell in the top bar opens |
| 311 | [g1t.sh/notifications](https://g1t.sh/notifications): every thread, a page |
| 312 | at a time, under the same tabs. Its sidebar chooses what you look at: |
| 313 | |
| 314 | | In the sidebar | Shows | |
| 315 | | --- | --- | |
| 316 | | **Everything** | Threads you have not marked done, with how many are unread | |
| 317 | | **Saved** | Threads you saved, done or not | |
| 318 | | **Done** | Threads you marked done. Select ↶ on one to move it back | |
| 319 | | **Why you were told** | Only threads told for one [reason](#reasons), or **Any reason** | |
| 320 | |
| 321 | The reason is kept in the address as `?reason=`, such as |
| 322 | [g1t.sh/notifications?reason=review_requested](https://g1t.sh/notifications?reason=review_requested), |
| 323 | so you can bookmark it. On a phone, and on a narrow window, where the |
| 324 | sidebar is a drawer, the page shows the views as tabs and the reason as a |
| 325 | menu above the list. |
| 326 | |
| 327 | ## Work through it |
| 328 | |
| 329 | 1. Open the Notifications page, or select the bell in the page's header to |
| 330 | work through them in a panel beside the page. |
| 331 | 2. Select an item to open what it is about. It is marked read, and the |
| 332 | panel closes. |
| 333 | 3. Point at an item (on a phone, the buttons are always there) to act on it |
| 334 | without opening it: |
| 335 | |
| 336 | | Action | What it does | |
| 337 | | --- | --- | |
| 338 | | **Done** (✓) | Moves the thread out of Everything and into Done, until something new happens on it | |
| 339 | | **Mark as read** / **Mark as unread** | Changes whether it counts as unread | |
| 340 | | **Save** | Keeps it under Saved, even after it is done | |
| 341 | | **Snooze until** | Hides it for 3 hours, until tomorrow, or for a week, then brings it back | |
| 342 | |
| 343 | **Mark all read** marks everything under the tab you are on as read. |
| 344 | **Open Notifications**, at the foot of the panel, goes to the page. |
| 345 | |
| 346 | [Home](/guides/home/) shows the unread warnings and failures waiting on you, |
| 347 | with what else needs you across the workspace. |
| 348 | |
| 349 | ## From the API and agents |
| 350 | |
| 351 | Everything here is also in the REST API and the MCP server, for a personal |
| 352 | access token or an OAuth sign-in. A workspace's token cannot use it, and |
| 353 | neither can g1t's own agents: they act as `g1t`, which has no notifications. |
| 354 | Reading needs the `notifications:read` scope, and changing anything |
| 355 | `notifications:write`; the Agent [preset](/guides/authentication/#presets) |
| 356 | has both. |
| 357 | |
| 358 | | Route | MCP action | What it does | |
| 359 | | --- | --- | --- | |
| 360 | | [`GET /notifications`](/reference/api/notifications/list-notifications/) | `list` | Your unread threads, latest first. Filter by `reason`, `severity`, `participating`, `since` and `before`; `all` adds read ones; `view` lists `saved` or `done`. | |
| 361 | | [`PUT /notifications`](/reference/api/notifications/mark-notifications-read/) | `mark_all_read` | Mark everything read up to `last_read_at`. | |
| 362 | | [`GET /notifications/threads/{id}`](/reference/api/notifications/get-notification-thread/) | `get` | One thread, its last 10 activities, and your subscription. | |
| 363 | | [`PATCH /notifications/threads/{id}`](/reference/api/notifications/mark-thread-read/) | `mark_read` | Mark a thread read, or unread. | |
| 364 | | [`DELETE /notifications/threads/{id}`](/reference/api/notifications/mark-thread-done/) | `done` | Mark a thread done. | |
| 365 | | [`PUT /notifications/threads/{id}/saved`](/reference/api/notifications/save-thread/) | `save` | Save a thread; `DELETE` unsaves it. | |
| 366 | | [`PUT /notifications/threads/{id}/snooze`](/reference/api/notifications/snooze-thread/) | `snooze` | Snooze a thread until `until`; `DELETE` brings it back. | |
| 367 | | [`PUT /repos/{owner}/{name}/issues/{number}/subscription`](/reference/api/notifications/set-issue-subscription/) | `subscribe` | Subscribe to an issue or pull request, unsubscribe, or ignore it. `GET` reads it and `DELETE` unsubscribes. The same works at `/notifications/threads/{id}/subscription`. | |
| 368 | | [`PUT /repos/{owner}/{name}/subscription`](/reference/api/notifications/set-repo-subscription/) | `watch` | Watch a repository at a `level`. `GET` reads it and `DELETE` goes back to the default. | |
| 369 | | [`GET /user/subscriptions`](/reference/api/notifications/list-watched-repos/) | `watched` | The repositories you watch other than the default way. | |
| 370 | |
| 371 | `GET /repos/{owner}/{name}/notifications` and |
| 372 | `PUT /repos/{owner}/{name}/notifications` list and mark one repository's |
| 373 | threads. Every action of the `notifications` tool is in |
| 374 | [MCP tools](/reference/mcp/#notifications). |
| 375 | |
| 376 | For example, to list the reviews waiting on you: |
| 377 | |
| 378 | ```sh |
| 379 | curl "https://api.g1t.sh/notifications?reason=review_requested" \ |
| 380 | -H "Authorization: Bearer $G1T_TOKEN" |
| 381 | ``` |
| 382 | |
| 383 | ## How long items are kept |
| 384 | |
| 385 | Threads you mark done are removed 30 days after you mark them. Any other |
| 386 | thread is removed once nothing has happened on it for 180 days. Saved |
| 387 | threads are kept until you unsave them. |