Inbox filters

You can create custom filters for your inbox using the following supported filters. For more information about creating custom filters, see 받은 편지함에서 알림 관리.

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 the is:issue, is:pr, and is: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
• Search exclusion using NOT or -QUALIFIER

Supported queries for custom filters

These are the types of filters that you can use:

• Filter by repository with repo:
• Filter by discussion type with is:
• Filter by notification reason with reason:

Supported repo: queries

To 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.

Supported is: queries

To 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.

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

For information about reducing noise from notifications for Dependabot alerts, see Dependabot 알림에 대한 경고 구성.

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

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

Supported reason: queries

To 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 알림 정보.

Query	Description
reason:assign	When there's an update on an issue or pull request you've been assigned to.
reason:author	When you opened a pull request or issue and there has been an update or new comment.
reason:comment	When you commented on an issue or pull request.
reason:participating	When you have commented on an issue or pull request or you have been @mentioned.
reason:invitation	When you're invited to a team, organization, or repository.
reason:manual	When you click Subscribe on an issue or pull request you weren't already subscribed to.
reason:mention	You were directly @mentioned.
reason:review-requested	You or a team you're on have been requested to review a pull request.
reason:security-alert	When a security alert is issued for a repository.
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.
reason:team-mention	When a team you're a member of is @mentioned.
reason:ci-activity	When a repository has a CI update, such as a new workflow run status.

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, see Dependabot 경고 정보.