You can create custom filters for your inbox using the following supported filters. For more information about creating custom filters, seeManaging notifications from your inbox.

Custom filter limitations

Custom filters do not currently support:

• Full text search in your inbox, including searching for pull request or issue titles
• Distinguishing between theis:issue,is:pr, andis:pull-request query filters. These queries will return both issues and pull requests.
• Creating more than 15 custom filters
• Changing the default filters or their order
• Searchexclusion usingNOT or-QUALIFIER

Supported queries for custom filters

These are the types of filters that you can use:

• Filter by repository withrepo:
• Filter by discussion type withis:
• Filter by notification reason withreason:
• Filter by notification author withauthor:
• Filter by organization withorg:

Supportedrepo: queries

To add arepo: 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.

Supportedis: queries

To filter notifications for specific activity on GitHub, you can use theis query. For example, to only see repository invitation updates, useis:repository-invitation, and to only see Dependabot alerts, useis:repository-vulnerability-alert.

• is:check-suite
• is:commit
• is:gist
• is:issue-or-pull-request
• is:release
• is:repository-invitation
• is:repository-vulnerability-alert
• is:repository-advisory
• is:discussion

For information about reducing noise from notifications for Dependabot alerts, seeConfiguring notifications for Dependabot alerts.

You can also use theis: query to describe how the notification was triaged.

• is:saved
• is:done
• is:unread
• is:read

Supportedreason: queries

To filter notifications by why you've received an update, you can use thereason: query. For example, to see notifications when you (or a team you're on) is requested to review a pull request, usereason:review-requested. For more information, seeAbout notifications.

Supportedauthor: queries

To filter notifications by user, you can use theauthor: query. An author is the original author of the thread (for example: in an issue, pull request, gist, or discussion) for which you are being notified. For example, to see notifications for threads created by the Octocat user, useauthor:octocat.

Supportedorg: queries

To filter notifications by organization, you can use theorg query. The organization you need to specify in the query is the organization of the repository for which you are being notified on GitHub. This query is useful if you belong to several organizations, and want to see notifications for a specific organization.

For example, to see notifications from the octo-org organization, useorg:octo-org.

Dependabot custom filters

If you use Dependabot to keep your dependencies up to date, you can use and save these custom filters:

• is:repository_vulnerability_alert to show notifications for Dependabot alerts.
• reason:security_alert to show notifications for Dependabot alerts and security update pull requests.
• author:app/dependabot to show notifications generated by Dependabot. This includes Dependabot alerts, security update pull requests, and version update pull requests.

For more information about Dependabot, seeAbout Dependabot alerts.