Searching discussions

You can search for discussions on GitHub and narrow the results using search qualifiers.

About searching for discussions

You can search for discussions globally across all of GitHub, or search for discussions within a particular organization or repository. For more information, see "About searching on GitHub."

Tips:

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

Search by the title, body, or comments

With the in qualifier you can restrict your search for discussions to the title, body, or comments. You can also combine qualifiers to search a combination of title, body, or comments. When you omit the in qualifier, GitHub searches the title, body, and comments.

QualifierExample
in:titlewelcome in:title matches discussions with "welcome" in the title.
in:bodyonboard in:title,body matches discussions with "onboard" in the title or body.
in:commentsthanks in:comments matches discussions with "thanks" in the comments for the discussion.

Search within a user's or organization's repositories

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

QualifierExample
user:USERNAMEuser:octocat feedback matches discussions with the word "feedback" from repositories owned by @octocat.
org:ORGNAMEorg:github matches discussions in repositories owned by the GitHub organization.
repo:USERNAME/REPOSITORYrepo:nodejs/node created:<2021-01-01 matches discussions from @nodejs' Node.js runtime project that were created before January 2021.

Filter by repository visibility

You can filter by the visibility of the repository containing the discussions using the is qualifier. For more information, see "About repositories."

QualifierExample
is:publicis:public matches discussions in public repositories.
is:internalis:internal matches discussions in internal repositories.
is:privateis:private tiramisu matches discussions that contain the word "tiramisu" in private repositories you can access.

Search by author

The author qualifier finds discussions created by a certain user.

QualifierExample
author:USERNAMEcool author:octocat matches discussions with the word "cool" that were created by @octocat.
bootstrap in:body author:octocat matches discussions created by @octocat that contain the word "bootstrap" in the body.

Search by commenter

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

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

Search by a user that's involved in a discussion

You can use the involves qualifier to find discussions that involve a certain user. The qualifier returns discussions that were either created by a certain user, mention the user, or contain comments by the user. The involves qualifier is a logical OR between the author, mentions, and commenter qualifiers for a single user.

QualifierExample
involves:USERNAMEinvolves:becca involves:octocat matches discussions either @becca or @octocat are involved in.
NOT beta in:body involves:becca matches discussions @becca is involved in that do not contain the word "beta" in the body.

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. For more information, see "Understanding the search syntax."

QualifierExample
comments:ncomments:>100 matches discussions with more than 100 comments.
comments:500..1000 matches discussions with comments ranging from 500 to 1,000.

Search by number of interactions

You can filter discussions 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 a discussion. For more information, see "Understanding the search syntax."

QualifierExample
interactions:n interactions:>2000 matches discussions with more than 2,000 interactions.
interactions:500..1000 matches discussions with interactions ranging from 500 to 1,000.

Search by number of reactions

You can filter discussions by the number of reactions using the reactions qualifier along with greater than, less than, and range qualifiers. For more information, see "Understanding the search syntax."

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

Search by when a discussion was created or last updated

You can filter discussions based on times of creation, or when the discussion was last updated. For discussion creation, you can use the created qualifier; to find out when an discussion was last updated, use the updated qualifier.

Both qualifiers 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).

When you search for a date, you can use greater than, less than, and range qualifiers to further filter results. For more information, see "Understanding the search syntax."

QualifierExample
created:YYYY-MM-DDcreated:>2020-11-15 matches discussions that were created after November 15, 2020.
updated:YYYY-MM-DDweird in:body updated:>=2020-02-01 matches discussions with the word "weird" in the body that were updated after December 2020.

Further reading

Did this doc help you?

Privacy policy

Help us make these docs great!

All GitHub docs are open source. See something that's wrong or unclear? Submit a pull request.

Make a contribution

Or, learn how to contribute.