You can also add optional time information THH:MM:SS+00:00 after the date, to search by the hour, minute, and second. Date formatting must follow the ISO8601 standard, which is YYYY-MM-DD (year-month-day). 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.īoth take a date as a parameter. You can filter issues based on times of creation, or when they were last updated. Search by when an issue or pull request was created or last updated Requested reviewers are no longer listed in the search results after they review a pull request. Type:pr team-review-requested:atom/design matches pull requests that have review requests from the team atom/design. 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 matches pull requests that you have directly been asked to review.
![mtasa window focus mtasa window focus](https://mobilelegend.vn/wp-content/uploads/2021/06/esim-la-sim-gi-1280x640.jpg)
![mtasa window focus mtasa window focus](http://duhocvungtau.com.vn/wp-content/uploads/2019/05/iNSOL05.jpg)
Type:pr review-requested:benbalter matches pull requests where a specific person is requested for review. Type:pr reviewed-by:gjtorikian matches pull requests reviewed by a particular person. Type:pr review:changes_requested matches pull requests in which a reviewer has asked for changes. Type:pr review:approved matches pull requests that a reviewer has approved. Type:pr review:required matches pull requests that require a review before they can be merged. Type:pr review:none matches pull requests that have not been reviewed.
![mtasa window focus mtasa window focus](https://insmac.org/uploads/posts/2017-12/1512308539_window-focus_01.jpg)
You can filter pull requests based on their review status ( none, required, approved, or changes requested), by reviewer, and by requested reviewer. Search by pull request review status and reviewer For more information, see " About pull requests." Qualifierĭraft:false matches pull requests that are ready for review. Reactions:500.1000 matches issues with reactions ranging from 500 to 1,000. Reactions:>1000 matches issues with more than 1000 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. Interactions:500.1000 matches pull requests or issues with interactions ranging from 500 to 1,000. Interactions:>2000 matches pull requests or issues with more than 2000 interactions. The interactions count is the number of reactions and comments on an issue or pull request. 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. Repo:mozilla/shumway created:100 matches closed issues with more than 100 comments.Ĭomments:500.1000 matches issues with comments ranging from 500 to 1,000. Org:github matches issues in repositories owned by the GitHub organization. User:defunkt ubuntu matches issues with the word "ubuntu" from repositories owned by ORGNAME If you have access to pull requests in more than 10,000 repositories, you will need to limit your search to a specific organization, user account, or repository to see results. To search issues and pull requests in a specific repository, you can use the repo qualifier. To search issues and pull requests in all repositories owned by a certain user or organization, you can use the user or org qualifier. Search within a user's or organization's repositories Shipit in:comments matches issues mentioning "shipit" in their comments. Warning in:title matches issues with "warning" in their title.Įrror in:title,body matches issues with "error" in their title or body. When you omit this qualifier, the title, body, and comments are all searched. With the in qualifier you can restrict your search to the title, body, comments, or any combination of these. Is:issue label:bug is:closed matches closed issues with the label "bug." Github commenter:defunkt type:issue matches issues that contain the word "github," and have a comment by is:pr matches pull requests with the word "event."
![mtasa window focus mtasa window focus](https://i1.rgstatic.net/publication/349483997_Introduction_to_Covid_Stories_from_East_Africa_and_Beyond_Lived_experiences_and_forward-looking_reflections_2020/links/603293d0299bf1cc26e06ec5/largepreview.png)
QualifierĬat type:pr matches pull requests with the word "cat." However, you can restrict search results to just issues or pull requests using the type or is qualifier. For more information, see " Keyboard shortcuts."īy default, GitHub search will return both issues and pull requests. You can focus your cursor on the search bar above the issue or pull request list with a keyboard shortcut. For example, if you want to search for issues with the label "In progress," you'd search for label:"in progress". Use quotations around multi-word search terms. For a list of search syntaxes that you can add to any search qualifier to further improve your results, see " Understanding the search syntax".