Article version: Enterprise Server 2.20

Searching issues and pull requests

You can search for issues and pull requests on GitHub Enterprise and narrow the results using these search qualifiers in any combination.

In this article

You can search for issues and pull requests globally across all of GitHub Enterprise, or search for issues and pull requests within a particular organization. For more information, see "About searching on GitHub."

Tips:

  • This article contains example searches on the GitHub.com website, but you can use the same search filters on your GitHub Enterprise Server instance.

  • For a list of search syntaxes that you can add to any search qualifier to further improve your results, see "Understanding the search syntax".

  • Use quotations around multi-word search terms. For example, if you want to search for issues with the label "In progress," you'd search for label:"in progress". Search is not case sensitive.

  • You can focus your cursor on the search bar above the issue or pull request list with a keyboard shortcut. For more information, see "Keyboard shortcuts."

Search only issues or pull requests

By default, GitHub Enterprise search will return both issues and pull requests. However, you can restrict search results to just issues or pull requests using the type or is qualifier.

QualifierExample
type:prcat type:pr matches pull requests with the word "cat."
type:issuegithub commenter:defunkt type:issue matches issues that contain the word "github," and have a comment by @defunkt.
is:prevent is:pr matches pull requests with the word "event."
is:issueis:issue label:bug is:closed matches closed issues with the label "bug."

Search by the title, body, or comments

With the in qualifier you can restrict your search to the title, body, comments, or any combination of these. When you omit this qualifier, the title, body, and comments are all searched.

QualifierExample
in:titlewarning in:title matches issues with "warning" in their title.
in:bodyerror in:title,body matches issues with "error" in their title or body.
in:commentsshipit in:comments matches issues mentioning "shipit" in their comments.

Search within a user's or organization's repositories

To search issues and pull requests in all repositories owned by a certain user or organization, you can use the user or org qualifier. To search issues and pull requests in a specific repository, you can use the repo qualifier.

QualifierExample
user:USERNAMEuser:defunkt ubuntu matches issues with the word "ubuntu" from repositories owned by @defunkt.
org:ORGNAMEorg:github matches issues in repositories owned by the GitHub organization.
repo:USERNAME/REPOSITORYrepo:mozilla/shumway created:<2012-03-01 matches issues from @mozilla's shumway project that were created before March 2012.

Search by open or closed state

You can filter issues and pull requests based on whether they're open or closed using the state or is qualifier.

QualifierExample
state:openlibraries state:open mentions:vmg matches open issues that mention @vmg with the word "libraries."
state:closeddesign state:closed in:body matches closed issues with the word "design" in the body.
is:openperformance is:open is:issue matches open issues with the word "performance."
is:closedandroid is:closed matches closed issues and pull requests with the word "android."

Search by public or private repository

If you're searching across all of GitHub Enterprise, it can be helpful to filter your results based on whether the repository is public or private. You can do this with is:public and is:private.

QualifierExample
is:publicis:public matches issues and pull requests in all public repositories.
is:privateis:private cupcake matches issues and pull requests that contain the word "cupcake" in private repositories you have access to.

Search by author

The author qualifier finds issues and pull requests created by a certain user or integration account.

QualifierExample
author:USERNAMEcool author:gjtorikian matches issues and pull requests with the word "cool" that were created by @gjtorikian.
bootstrap in:body author:mdo matches issues written by @mdo that contain the word "bootstrap" in the body.
author:app/USERNAMEauthor:app/robot matches issues created by the integration account named "robot."

Search by assignee

The assignee qualifier finds issues and pull requests that are assigned to a certain user. You cannot search for issues and pull requests that have any assignee, however, you can search for issues and pull requests that have no assignee.

QualifierExample
assignee:USERNAMEassignee:vmg repo:libgit2/libgit2 matches issues and pull requests in libgit2's project libgit2 that are assigned to @vmg.

Search by mention

The mentions qualifier finds issues that mention a certain user. For more information, see "Mentioning people and teams."

QualifierExample
mentions:USERNAMEresque mentions:defunkt matches issues with the word "resque" that mention @defunkt.

Search by team mention

For organizations and teams you belong to, you can use the team qualifier to find issues or pull requests that @mention a certain team within that organization. Replace these sample names with your organization and team name to perform a search.

QualifierExample
team:ORGNAME/TEAMNAMEteam:jekyll/owners matches issues where the @jekyll/owners team is mentioned.
team:myorg/ops is:open is:pr matches open pull requests where the @myorg/ops team is mentioned.

Search by commenter

The commenter qualifier finds issues that contain a comment from a certain user.

QualifierExample
commenter:USERNAMEgithub commenter:defunkt org:github matches issues in repositories owned by GitHub, that contain the word "github," and have a comment by @defunkt.

Search by a user that's involved in an issue or pull request

You can use the involves qualifier to find issues that in some way involve a certain user. The involves qualifier is a logical OR between the author, assignee, mentions, and commenter qualifiers for a single user. In other words, this qualifier finds issues and pull requests that were either created by a certain user, assigned to that user, mention that user, or were commented on by that user.

QualifierExample
involves:USERNAMEinvolves:defunkt involves:jlord matches issues either @defunkt or @jlord are involved in.
NOT bootstrap in:body involves:mdo matches issues @mdo is involved in that do not contain the word "bootstrap" in the body.

Search by label

You can narrow your results by labels, using the label qualifier. Since issues can have multiple labels, you can list a separate qualifier for each issue.

QualifierExample
label:LABELlabel:"help wanted" language:ruby matches issues with the label "help wanted" that are in Ruby repositories.
broken in:body -label:bug label:priority matches issues with the word "broken" in the body, that lack the label "bug", but do have the label "priority."
label:bug label:resolved matches issues with the labels "bug" and "resolved."

Search by milestone

The milestone qualifier finds issues or pull requests that are a part of a milestone within a repository.

QualifierExample
milestone:MILESTONEmilestone:"overhaul" matches issues that are in a milestone named "overhaul."
milestone:"bug fix" matches issues that are in a milestone named "bug fix."

Search by project board

You can use the project qualifier to find issues that are associated with a specific project board in a repository or organization. You must search project boards by the project board number. You can find the project board number at the end of a project board's URL.

QualifierExample
project:PROJECT_BOARDproject:github/57 matches issues owned by GitHub that are associated with the organization's project board 57.
project:REPOSITORY/PROJECT_BOARDproject:github/linguist/1 matches issues that are associated with project board 1 in @github's linguist repository.

Search by commit status

You can filter pull requests based on the status of the commits. This is especially useful if you are using the Status API or a CI service.

QualifierExample
status:pendinglanguage:go status:pending matches pull requests opened into Go repositories where the status is pending.
status:successis:open status:success finally in:body matches open pull requests with the word "finally" in the body with a successful status.
status:failurecreated:2015-05-01..2015-05-30 status:failure matches pull requests opened on May 2015 with a failed status.

Search by commit SHA

If you know the specific SHA hash of a commit, you can use it to search for pull requests that contain that SHA. The SHA syntax must be at least seven characters.

QualifierExample
SHAe1109ab matches pull requests with a commit SHA that starts with e1109ab.
0eff326d6213c is:merged matches merged pull requests with a commit SHA that starts with 0eff326d6213c.

Search by branch name

You can filter pull requests based on the branch they came from (the "head" branch) or the branch they are merging into (the "base" branch).

QualifierExample
head:HEAD_BRANCHhead:change is:closed is:unmerged matches pull requests opened from branch names beginning with the word "change" that are closed.
base:BASE_BRANCHbase:gh-pages matches pull requests that are being merged into the gh-pages branch.

Search by language

With the language qualifier you can search for issues and pull requests within repositories that are written in a certain language.

QualifierExample
language:LANGUAGElanguage:ruby state:open matches open issues that are in Ruby repositories.

Search by number of comments

You can use the comments qualifier along with greater than, less than, and range qualifiers to search by the number of comments.

QualifierExample
comments:nstate:closed comments:>100 matches closed issues with more than 100 comments.
comments:500..1000 matches issues with comments ranging from 500 to 1,000.

Search by number of interactions

You can filter issues and pull requests by the number of interactions with the interactions qualifier along with greater than, less than, and range qualifiers. The interactions count is the number of reactions and comments on an issue or pull request.

QualifierExample
interactions:n interactions:>2000 matches pull requests or issues with more than 2000 interactions.
interactions:500..1000 matches pull requests or issues with interactions ranging from 500 to 1,000.

Search by number of reactions

You can filter issues and pull requests by the number of reactions using the reactions qualifier along with greater than, less than, and range qualifiers.

QualifierExample
reactions:n reactions:>1000 matches issues with more than 1000 reactions.
reactions:500..1000 matches issues with reactions ranging from 500 to 1,000.

Search for draft pull requests

You can filter for draft pull requests. For more information, see "About pull requests."

QualifierExample
is:draftis:draft matches draft pull requests.

Search by pull request review status and reviewer

You can filter pull requests based on their review status (none, required, approved, or changes requested), by reviewer, and by requested reviewer.

QualifierExample
review:nonetype:pr review:none matches pull requests that have not been reviewed.
review:requiredtype:pr review:required matches pull requests that require a review before they can be merged.
review:approvedtype:pr review:approved matches pull requests that a reviewer has approved.
review:changes_requestedtype:pr review:changes_requested matches pull requests in which a reviewer has asked for changes.
reviewed-by:USERNAMEtype:pr reviewed-by:gjtorikian matches pull requests reviewed by a particular person.
review-requested:USERNAMEtype:pr review-requested:benbalter matches pull requests where a specific person is requested for review. Requested reviewers are no longer listed in the search results after they review a pull request. If the requested person is on a team that is requested for review, then review requests for that team will also appear in the search results.
team-review-requested:TEAMNAMEtype:pr team-review-requested:atom/design matches pull requests that have review requests from the team atom/design. Requested reviewers are no longer listed in the search results after they review a pull request.

Search by when an issue or pull request was created or last updated

You can filter issues based on times of creation, or when they were last updated. For issue creation, you can use the created qualifier; to find out when an issue was last updated, you'll want to use the updated qualifier.

Both take a date as a parameter. Date formatting must follow the ISO8601 standard, which is YYYY-MM-DD (year-month-day). You can also add optional time information THH:MM:SS+00:00 after the date, to search by the hour, minute, and second. That's T, followed by HH:MM:SS (hour-minutes-seconds), and a UTC offset (+00:00).

Dates support greater than, less than, and range qualifiers.

QualifierExample
created:YYYY-MM-DDlanguage:c# created:<2011-01-01 state:open matches open issues that were created before 2011 in repositories written in C#.
updated:YYYY-MM-DDweird in:body updated:>=2013-02-01 matches issues with the word "weird" in the body that were updated after February 2013.

Search by when an issue or pull request was closed

You can filter issues and pull requests based on when they were closed, using the closed qualifier.

This qualifier takes a date as its parameter. Date formatting must follow the ISO8601 standard, which is YYYY-MM-DD (year-month-day). You can also add optional time information THH:MM:SS+00:00 after the date, to search by the hour, minute, and second. That's T, followed by HH:MM:SS (hour-minutes-seconds), and a UTC offset (+00:00).

Dates support greater than, less than, and range qualifiers.

QualifierExample
closed:YYYY-MM-DDlanguage:swift closed:>2014-06-11 matches issues and pull requests in Swift that were closed after June 11, 2014.
data in:body closed:<2012-10-01 matches issues and pull requests with the word "data" in the body that were closed before October 2012.

Search by when a pull request was merged

You can filter pull requests based on when they were merged, using the merged qualifier.

This qualifier takes a date as its parameter. Date formatting must follow the ISO8601 standard, which is YYYY-MM-DD (year-month-day). You can also add optional time information THH:MM:SS+00:00 after the date, to search by the hour, minute, and second. That's T, followed by HH:MM:SS (hour-minutes-seconds), and a UTC offset (+00:00).

Dates support greater than, less than, and range qualifiers.

QualifierExample
merged:YYYY-MM-DDlanguage:javascript merged:<2011-01-01 matches pull requests in JavaScript repositories that were merged before 2011.
fast in:title language:ruby merged:>=2014-05-01 matches pull requests in Ruby with the word "fast" in the title that were merged after May 2014.

Search based on whether a pull request is merged or unmerged

You can filter pull requests based on whether they're merged or unmerged using the is qualifier.

QualifierExample
is:mergedbugfix is:pr is:merged matches merged pull requests with the word "bugfix."
is:unmergederror is:unmerged matches closed issues and pull requests with the word "error."

Search based on whether a repository is archived

The archived qualifier filters your results based on whether an issue or pull request is in an archived repository.

QualifierExample
archived:truearchived:true GNOME matches issues and pull requests that contain the word "GNOME" in archived repositories you have access to.
archived:falsearchived:false GNOME matches issues and pull requests that contain the word "GNOME" in unarchived repositories you have access to.

Search based on whether a conversation is locked

You can search for an issue or pull request that has a locked conversation using the is qualifier. For more information, see "Locking conversations."

QualifierExample
is:lockedcode of conduct is:locked is:issue archived:false matches issues or pull requests with the words "code of conduct" that have a locked conversation in a repository that is not archived.
is:unlockedcode of conduct is:unlocked is:issue archived:false matches issues or pull requests with the words "code of conduct" that have an unlocked conversation in a repository that is not archived.

Search by missing metadata

You can narrow your search to issues and pull requests that are missing certain metadata, using the no qualifier. That metadata includes:

  • Labels
  • Milestones
  • Assignees
  • Projects
QualifierExample
no:labelpriority no:label matches issues and pull requests with the word "priority" that also don't have any labels.
no:milestonesprint no:milestone type:issue matches issues not associated with a milestone containing the word "sprint."
no:assigneeimportant no:assignee language:java type:issue matches issues not associated with an assignee, containing the word "important," and in Java repositories.
no:projectbuild no:project matches issues not associated with a project board, containing the word "build."

Further reading

Ask a human

Can't find what you're looking for?

Contact us