{"meta":{"title":"Inbox filters","intro":"Learn about filtering notifications in your GitHub inbox.","product":"Subscriptions & notifications","breadcrumbs":[{"href":"/en/enterprise-server@3.22/subscriptions-and-notifications","title":"Subscriptions & notifications"},{"href":"/en/enterprise-server@3.22/subscriptions-and-notifications/reference","title":"Reference"},{"href":"/en/enterprise-server@3.22/subscriptions-and-notifications/reference/inbox-filters","title":"Inbox filters"}],"documentType":"article"},"body":"# Inbox filters\n\nLearn about filtering notifications in your GitHub inbox.\n\nYou can create custom filters for your inbox using the following supported filters. For more information about creating custom filters, see [Managing notifications from your inbox](/en/enterprise-server@3.22/subscriptions-and-notifications/how-tos/viewing-and-triaging-notifications/managing-notifications-from-your-inbox#customizing-your-inbox-with-custom-filters).\n\n## Custom filter limitations\n\nCustom filters do not currently support:\n\n* Full text search in your inbox, including searching for pull request or issue titles\n* Distinguishing between the `is:issue`, `is:pr`, and `is:pull-request` query filters. These queries will return both issues and pull requests.\n* Creating more than 15 custom filters\n* Changing the default filters or their order\n* Search [exclusion](/en/enterprise-server@3.22/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax) using `NOT` or `-QUALIFIER`\n\n## Supported queries for custom filters\n\nThese are the types of filters that you can use:\n\n* Filter by repository with `repo:`\n* Filter by discussion type with `is:`\n* Filter by notification reason with `reason:`\n\n### Supported `repo:` queries\n\nTo add a `repo:` filter, you must include the owner of the repository in the query: `repo:owner/repository`. An owner is the organization or the user who owns the GitHub asset that triggers the notification. For example, `repo:octo-org/octo-repo` will show notifications triggered in the octo-repo repository within the octo-org organization.\n\n### Supported `is:` queries\n\nTo filter notifications for specific activity on GitHub, you can use the `is` query. For example, to only see repository invitation updates, use `is:repository-invitation`, and to only see Dependabot alerts, use `is:repository-vulnerability-alert`.\n\n* `is:check-suite`\n* `is:commit`\n* `is:gist`\n* `is:issue-or-pull-request`\n* `is:release`\n* `is:repository-invitation`\n* `is:repository-vulnerability-alert`\n\nFor information about reducing noise from notifications for Dependabot alerts, see [Configuring notifications for Dependabot alerts](/en/enterprise-server@3.22/code-security/how-tos/secure-your-supply-chain/manage-your-dependency-security/configure-dependabot-notifications).\n\nYou can also use the `is:` query to describe how the notification was triaged.\n\n* `is:saved`\n* `is:done`\n* `is:unread`\n* `is:read`\n\n### Supported `reason:` queries\n\nTo filter notifications by why you've received an update, you can use the `reason:` query. For example, to see notifications when you (or a team you're on) is requested to review a pull request, use `reason:review-requested`. For more information, see [About notifications](/en/enterprise-server@3.22/subscriptions-and-notifications/concepts/about-notifications#reasons-for-receiving-notifications).\n\n| Query                     | Description                                                                                                        |\n| ------------------------- | ------------------------------------------------------------------------------------------------------------------ |\n| `reason:assign`           | When there's an update on an issue or pull request you've been assigned to.                                        |\n| `reason:author`           | When you opened a pull request or issue and there has been an update or new comment.                               |\n| `reason:comment`          | When you commented on an issue or pull request.                                                                    |\n| `reason:participating`    | When you have commented on an issue or pull request or you have been @mentioned.                                   |\n| `reason:invitation`       | When you're invited to a team, organization, or repository.                                                        |\n| `reason:manual`           | When you click **Subscribe** on an issue or pull request you weren't already subscribed to.                        |\n| `reason:mention`          | You were directly @mentioned.                                                                                      |\n| `reason:review-requested` | You or a team you're on have been requested to review a pull request.                                              |\n| `reason:security-alert`   | When a security alert is issued for a repository.                                                                  |\n| `reason:state-change`     | When the state of a pull request or issue is changed. For example, an issue is closed or a pull request is merged. |\n| `reason:team-mention`     | When a team you're a member of is @mentioned.                                                                      |\n| `reason:ci-activity`      | When a repository has a CI update, such as a new workflow run status.                                              |\n\n## Dependabot custom filters\n\nIf you use Dependabot to keep your dependencies up to date, you can use and save these custom filters:\n\n* `is:repository_vulnerability_alert` to show notifications for Dependabot alerts.\n* `reason:security_alert` to show notifications for Dependabot alerts and security update pull requests.\n* `author:app/dependabot` to show notifications generated by Dependabot. This includes Dependabot alerts, security update pull requests, and version update pull requests.\n\nFor more information about Dependabot, see [Dependabot alerts](/en/enterprise-server@3.22/code-security/concepts/supply-chain-security/dependabot-alerts)."}