Searching issues with module name

Core Development
21

Link back to Adjusting the "Triager" role's permissions · Issue #460 · python/core-workflow · GitHub

A

1 Like
22

Just to be clear for anyone following this but not the other channels, the fine-grained permissions seem almost exclusively tailored for corporate users, and none of them ended up being particularly useful for triagers that they didn’t already have (despite a number of missing perms that would clearly be useful).

However, @encukou did mention on another thread that teams can be added to projects, which could presumably include triagers.

23

bpo indexed and allowed search of issue text. AFAIK, gh does not. But gh does search titles. So I think issues about one module (or obvious group like tkinter, email, and idle) should routinely have the module/group name in the title. I routinely rewrite issue title, and routinely add something more identifying than just ‘IDLE’.

24

It does. For example, gh-81544 will appear in your search results if you search for “sqlite3”.

However, it failed to return correct search if the query exceeded a certain amount of characters[1]. For example, searching for a long test method name would very often return an empty result; this led me to creating duplicate issues for failing buildbots. The GitHub search is far less buggy and far more accurate, in my experience.

I think that is good practice, regardless of if the issue search is buggy or not.

  1. I don’t know what the limit was ↩︎

1 Like
25

You can limit GitHub issue search by title, body or comment:

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.

Qualifier Example
in:title warning in:title matches issues with “warning” in their title.
in:body error in:title,body matches issues with “error” in their title or body.
in:comments shipit in:comments matches issues mentioning “shipit” in their comments.
3 Likes