This site shows the issues across all the various GitHub orgs that make up .NET, such as aspnet, dotnet, and nuget.

• We should consider using a stop list to avoid indexing super common words, such as "the".
• Find a way to incrementally update the trie so that we can offer quasi real-time indexing based on web hook events.

• We should support all of GitHub's query syntax
  • It seems some of them use and while some use or semantics. For example, involves uses or while label uses and.
  • Looks like we need a text match with an in qualifer:
    • test in:title,body means "search in title and body"
    • developer dependency in:title means "search for developer and dependency in title only"
    • Hmm, looks like in is just a global modifer, for example developer in:body console in:title means "search for console and developer in either body or title".
  • Do all key value pairs support commas or just in?
  • in:title
  • in:body
  • in:comments
  • repo:{org/repo}
  • is:public
  • is:internal
  • is:private
  • mentions:{user}
  • team:{orgname}/{teamName}
  • commenter:{user}
  • involves:{user}
  • linked:pr
  • linked:issue
  • project:{project}
  • status:pending
  • status:success
  • status:failure
  • {sha}
  • head:{branch}
  • base:{branch}
  • comments:{range} (range is n, <n, <=n, >n, >=n, or n..m)
  • reactions:{range}
  • interactions:{range} (interactions := reactions + comments)
  • review:none
  • review:required
  • review:approved
  • review:changes_requested
  • reviewed-by:{user}
  • review-requested:{user}
  • team-review-requested:{user}
  • created:{range}
  • updated:{range}
  • closed:{range}
  • merged:{range}
  • archived:true
  • archived:false
  • is:locked
  • is:unlocked
  • no:project
• We should support custom sorting
  • sort:comments-asc
  • sort:comments-desc
  • sort:reactions-{reaction}-asc where {reaction} is +1, -1, smile, tada, heart, thinking_face, rocket, eyes
  • sort:reactions-{reaction}-desc
• We should replace the JavaScript octo-icon library with static CSS-based icons because the JavaScript ones don't work well with Blazor (basically, it works on initial render but when the page gets updated, for example, due to paging, the icons aren't updated while hitting Ctrl+R fixes the problem).