Search

The search field at the top of Issues searches every repository in the workspace at once. Type into Search issues and results appear as you type.

What it matches

• Issue titles.
• Issue bodies.
• Label names.
• Issue numbers. Typing 412 finds issue 412 in any repository; typing acme/app#412 finds that one.

Matching is by word, not by substring: deploy matches “deploying” and “deployment”, and dep does not match either.

What it does not match

• Comments. A phrase that appears only in a comment is not found. Use the filters to narrow the list and open the issue.
• Code, files, pull requests or wikis.
• Anything in a repository outside the connection.

Search and filters together

Search is a filter like any other: it narrows whatever is already on screen. To search inside one repository, add the repository filter first. To save a search for later, save the view.

Why search does not go to GitHub

Pealboard searches its own copy of your issues rather than asking GitHub on every keystroke. GitHub’s issue search is limited to a small number of requests per minute per installation, which one person typing would use up. Searching the local copy means results appear immediately and no one’s typing can exhaust a budget everybody shares.

The copy is kept current by webhooks and repaired every hour, so a newly created issue is searchable within seconds of GitHub accepting it.