Re: Announcing githubsearch!

[Michael Sokolov]

No I think you only get one version. Maybe we can try adding the green
background out regular making it gray and keeping the transparent
background?

On Mon, Feb 26, 2024, 2:53 PM Michael McCandless 
wrote:

> Done!  Deployed!  Thank you Mike S.
>
> Though on my "dark mode" Chrome on a Macbook, it's super dark.  I can make
> it out but I gotta stare for a bit ... do they make light and dark mode
> .ico files in one!?
>
> Mike McCandless
>
> http://blog.mikemccandless.com
>
>
> On Sun, Feb 25, 2024 at 6:05 PM Michael Sokolov 
> wrote:
>
>> here is a favicon you might want to try: I cropped the "VL" from the
>> Apache Lucene logo (ok I guess it's an AL) -- if you save it as
>> favicon.ico in the root of your website (ie as url /favicon.ico) it
>> should show up in bookmarks, browser toolbars, etc as a handy memory
>> aid. Of course you might have other ideas for a picture - it's
>> actually pretty easy to make the favicon once you have a picture you
>> like; I followed the instructions here
>>
>> https://www.logikfabrik.se/blog/how-to-create-a-multisize-favicon-using-gimp/
>>
>> On Thu, Feb 22, 2024 at 10:48 AM Zhang Chao <80152...@qq.com.invalid>
>> wrote:
>> >
>> > Great job! Thanks Mike!
>> >
>> > 2024年2月22日 22:31，Alessandro Benedetti  写道：
>> >
>> > That's cool Mike! Well done!
>> >
>> > On Wed, 21 Feb 2024, 22:02 Anshum Gupta, 
>> wrote:
>> >>
>> >> This is great! Like always, thank you Mike!
>> >>
>> >> On Mon, Feb 19, 2024 at 8:40 AM Michael McCandless <
>> luc...@mikemccandless.com> wrote:
>> >>>
>> >>> Hi Team,
>> >>>
>> >>> ~1.5 years ago (August 2022) we migrated our Lucene issue tracking
>> from Jira to GitHub. Thank you Tomoko for all the hard work doing such a
>> complex, multi-phased, high-fidelity migration!
>> >>>
>> >>> I finally finished also migrating jirasearch to GitHub:
>> githubsearch.mikemccandless.com. It was tricky because GitHub issues/PRs
>> are fundamentally more complex than Jira's data model, and the GitHub REST
>> API is also quite rich / heavily normalized. All of the source code for
>> githubsearch lives here. The UI remains its barebones self ;)
>> >>>
>> >>> Githubsearch is dog food for us: it showcases Lucene (currently
>> 9.8.0), and many of its fun features like infix autosuggest, block join
>> queries (each comment is a sub-document on the issue/PR), DrillSideways
>> faceting, near-real-time indexing/searching, synonyms (try “oome”),
>> expressions, non-relevance and blended-relevance sort, etc.  (This old blog
>> post goes into detail.)  Plus, it’s meta-fun to use Lucene to search its
>> own issues, to help us be more productive in improving Lucene!  Nicely
>> recursive.
>> >>>
>> >>> In addition to good ol’ searching by text, githubsearch has some
>> new/fun features:
>> >>>
>> >>> Drill down to just PRs or issues
>> >>> Filter by “review requested” for a given user: poor Adrien has 8
>> (open) now (sorry)! Or see your mentions (Robert is mentioned in 27 open
>> issues/PRs). Or PRs that you reviewed (Uwe has reviewed 9 still-open PRs).
>> Or issues and PRs where a user has had any involvement at all (Dawid has
>> interacted on 197 issues/PRs).
>> >>> Find still-open PRs that were created by a New Contributor (an author
>> who has no changes merged into our repository) or Contributor
>> (non-committer who has had some changes merged into our repository) or
>> Member
>> >>> Here are the uber-stale (last touched more than a month ago) open PRs
>> by outside contributors. We should ideally keep this at 0, but it’s 83 now!
>> >>> “Link to this search” to get a short-er, more permanent URL (it is
>> NOT a URL shortener, though!)
>> >>> Save named searches you frequently run (they just save to local
>> cookie state on that one browser)
>> >>>
>> >>> I’m sure there are exciting bugs, feedback/patches welcome!  If you
>> see problems, please reply to this email or file an issue here.
>> >>>
>> >>> Note that jirasearch remains running, to search Solr, Tika and Infra
>> issues.
>> >>>
>> >>> Happy Searching,
>> >>>
>> >>> Mike McCandless
>> >>>
>> >>> http://blog.mikemccandless.com
>> >>
>> >>
>> >>
>> >> --
>> >> Anshum Gupta
>> >
>> >
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
>> For additional commands, e-mail: dev-h...@lucene.apache.org
>
>

Re: Announcing githubsearch!

[Michael McCandless]

Done!  Deployed!  Thank you Mike S.

Though on my "dark mode" Chrome on a Macbook, it's super dark.  I can make
it out but I gotta stare for a bit ... do they make light and dark mode
.ico files in one!?

Mike McCandless

http://blog.mikemccandless.com


On Sun, Feb 25, 2024 at 6:05 PM Michael Sokolov  wrote:

> here is a favicon you might want to try: I cropped the "VL" from the
> Apache Lucene logo (ok I guess it's an AL) -- if you save it as
> favicon.ico in the root of your website (ie as url /favicon.ico) it
> should show up in bookmarks, browser toolbars, etc as a handy memory
> aid. Of course you might have other ideas for a picture - it's
> actually pretty easy to make the favicon once you have a picture you
> like; I followed the instructions here
>
> https://www.logikfabrik.se/blog/how-to-create-a-multisize-favicon-using-gimp/
>
> On Thu, Feb 22, 2024 at 10:48 AM Zhang Chao <80152...@qq.com.invalid>
> wrote:
> >
> > Great job! Thanks Mike!
> >
> > 2024年2月22日 22:31，Alessandro Benedetti  写道：
> >
> > That's cool Mike! Well done!
> >
> > On Wed, 21 Feb 2024, 22:02 Anshum Gupta,  wrote:
> >>
> >> This is great! Like always, thank you Mike!
> >>
> >> On Mon, Feb 19, 2024 at 8:40 AM Michael McCandless <
> luc...@mikemccandless.com> wrote:
> >>>
> >>> Hi Team,
> >>>
> >>> ~1.5 years ago (August 2022) we migrated our Lucene issue tracking
> from Jira to GitHub. Thank you Tomoko for all the hard work doing such a
> complex, multi-phased, high-fidelity migration!
> >>>
> >>> I finally finished also migrating jirasearch to GitHub:
> githubsearch.mikemccandless.com. It was tricky because GitHub issues/PRs
> are fundamentally more complex than Jira's data model, and the GitHub REST
> API is also quite rich / heavily normalized. All of the source code for
> githubsearch lives here. The UI remains its barebones self ;)
> >>>
> >>> Githubsearch is dog food for us: it showcases Lucene (currently
> 9.8.0), and many of its fun features like infix autosuggest, block join
> queries (each comment is a sub-document on the issue/PR), DrillSideways
> faceting, near-real-time indexing/searching, synonyms (try “oome”),
> expressions, non-relevance and blended-relevance sort, etc.  (This old blog
> post goes into detail.)  Plus, it’s meta-fun to use Lucene to search its
> own issues, to help us be more productive in improving Lucene!  Nicely
> recursive.
> >>>
> >>> In addition to good ol’ searching by text, githubsearch has some
> new/fun features:
> >>>
> >>> Drill down to just PRs or issues
> >>> Filter by “review requested” for a given user: poor Adrien has 8
> (open) now (sorry)! Or see your mentions (Robert is mentioned in 27 open
> issues/PRs). Or PRs that you reviewed (Uwe has reviewed 9 still-open PRs).
> Or issues and PRs where a user has had any involvement at all (Dawid has
> interacted on 197 issues/PRs).
> >>> Find still-open PRs that were created by a New Contributor (an author
> who has no changes merged into our repository) or Contributor
> (non-committer who has had some changes merged into our repository) or
> Member
> >>> Here are the uber-stale (last touched more than a month ago) open PRs
> by outside contributors. We should ideally keep this at 0, but it’s 83 now!
> >>> “Link to this search” to get a short-er, more permanent URL (it is NOT
> a URL shortener, though!)
> >>> Save named searches you frequently run (they just save to local cookie
> state on that one browser)
> >>>
> >>> I’m sure there are exciting bugs, feedback/patches welcome!  If you
> see problems, please reply to this email or file an issue here.
> >>>
> >>> Note that jirasearch remains running, to search Solr, Tika and Infra
> issues.
> >>>
> >>> Happy Searching,
> >>>
> >>> Mike McCandless
> >>>
> >>> http://blog.mikemccandless.com
> >>
> >>
> >>
> >> --
> >> Anshum Gupta
> >
> >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> For additional commands, e-mail: dev-h...@lucene.apache.org

Re: Announcing githubsearch!

[Michael Sokolov]

here is a favicon you might want to try: I cropped the "VL" from the
Apache Lucene logo (ok I guess it's an AL) -- if you save it as
favicon.ico in the root of your website (ie as url /favicon.ico) it
should show up in bookmarks, browser toolbars, etc as a handy memory
aid. Of course you might have other ideas for a picture - it's
actually pretty easy to make the favicon once you have a picture you
like; I followed the instructions here
https://www.logikfabrik.se/blog/how-to-create-a-multisize-favicon-using-gimp/

On Thu, Feb 22, 2024 at 10:48 AM Zhang Chao <80152...@qq.com.invalid> wrote:
>
> Great job! Thanks Mike!
>
> 2024年2月22日 22:31，Alessandro Benedetti  写道：
>
> That's cool Mike! Well done!
>
> On Wed, 21 Feb 2024, 22:02 Anshum Gupta,  wrote:
>>
>> This is great! Like always, thank you Mike!
>>
>> On Mon, Feb 19, 2024 at 8:40 AM Michael McCandless 
>>  wrote:
>>>
>>> Hi Team,
>>>
>>> ~1.5 years ago (August 2022) we migrated our Lucene issue tracking from 
>>> Jira to GitHub. Thank you Tomoko for all the hard work doing such a 
>>> complex, multi-phased, high-fidelity migration!
>>>
>>> I finally finished also migrating jirasearch to GitHub: 
>>> githubsearch.mikemccandless.com. It was tricky because GitHub issues/PRs 
>>> are fundamentally more complex than Jira's data model, and the GitHub REST 
>>> API is also quite rich / heavily normalized. All of the source code for 
>>> githubsearch lives here. The UI remains its barebones self ;)
>>>
>>> Githubsearch is dog food for us: it showcases Lucene (currently 9.8.0), and 
>>> many of its fun features like infix autosuggest, block join queries (each 
>>> comment is a sub-document on the issue/PR), DrillSideways faceting, 
>>> near-real-time indexing/searching, synonyms (try “oome”), expressions, 
>>> non-relevance and blended-relevance sort, etc.  (This old blog post goes 
>>> into detail.)  Plus, it’s meta-fun to use Lucene to search its own issues, 
>>> to help us be more productive in improving Lucene!  Nicely recursive.
>>>
>>> In addition to good ol’ searching by text, githubsearch has some new/fun 
>>> features:
>>>
>>> Drill down to just PRs or issues
>>> Filter by “review requested” for a given user: poor Adrien has 8 (open) now 
>>> (sorry)! Or see your mentions (Robert is mentioned in 27 open issues/PRs). 
>>> Or PRs that you reviewed (Uwe has reviewed 9 still-open PRs). Or issues and 
>>> PRs where a user has had any involvement at all (Dawid has interacted on 
>>> 197 issues/PRs).
>>> Find still-open PRs that were created by a New Contributor (an author who 
>>> has no changes merged into our repository) or Contributor (non-committer 
>>> who has had some changes merged into our repository) or Member
>>> Here are the uber-stale (last touched more than a month ago) open PRs by 
>>> outside contributors. We should ideally keep this at 0, but it’s 83 now!
>>> “Link to this search” to get a short-er, more permanent URL (it is NOT a 
>>> URL shortener, though!)
>>> Save named searches you frequently run (they just save to local cookie 
>>> state on that one browser)
>>>
>>> I’m sure there are exciting bugs, feedback/patches welcome!  If you see 
>>> problems, please reply to this email or file an issue here.
>>>
>>> Note that jirasearch remains running, to search Solr, Tika and Infra issues.
>>>
>>> Happy Searching,
>>>
>>> Mike McCandless
>>>
>>> http://blog.mikemccandless.com
>>
>>
>>
>> --
>> Anshum Gupta
>
>

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Re: Announcing githubsearch!

[Zhang Chao]

Great job! Thanks Mike!

> 2024年2月22日 22:31，Alessandro Benedetti  写道：
> 
> That's cool Mike! Well done! 
> 
> On Wed, 21 Feb 2024, 22:02 Anshum Gupta,  > wrote:
>> This is great! Like always, thank you Mike! 
>> 
>> On Mon, Feb 19, 2024 at 8:40 AM Michael McCandless 
>> mailto:luc...@mikemccandless.com>> wrote:
>>> Hi Team,
>>> 
>>> ~1.5 years ago (August 2022) we migrated our Lucene issue tracking from 
>>> Jira to GitHub. Thank you Tomoko for all the hard work doing such a 
>>> complex, multi-phased, high-fidelity migration!
>>> 
>>> I finally finished also migrating jirasearch to GitHub: 
>>> githubsearch.mikemccandless.com . 
>>> It was tricky because GitHub issues/PRs are fundamentally more complex than 
>>> Jira's data model, and the GitHub REST API is also quite rich / heavily 
>>> normalized. All of the source code for githubsearch lives here 
>>> .
>>>  The UI remains its barebones self ;)
>>> 
>>> Githubsearch 
>>> 
>>>  is dog food for us: it showcases Lucene (currently 9.8.0), and many of its 
>>> fun features like infix autosuggest, block join queries (each comment is a 
>>> sub-document on the issue/PR), DrillSideways faceting, near-real-time 
>>> indexing/searching, synonyms (try “oome 
>>> ”),
>>>  expressions, non-relevance and blended-relevance sort, etc.  (This old 
>>> blog post 
>>> 
>>>  goes into detail.)  Plus, it’s meta-fun to use Lucene to search its own 
>>> issues, to help us be more productive in improving Lucene!  Nicely 
>>> recursive.
>>> 
>>> In addition to good ol’ searching by text, githubsearch 
>>>  has some new/fun features:
>>> Drill down to just PRs or issues
>>> Filter by “review requested” for a given user: poor Adrien has 8 (open) now 
>>> 
>>>  (sorry)! Or see your mentions (Robert is mentioned in 27 open issues/PRs 
>>> ).
>>>  Or PRs that you reviewed (Uwe has reviewed 9 still-open PRs 
>>> ).
>>>  Or issues and PRs where a user has had any involvement at all (Dawid has 
>>> interacted on 197 issues/PRs 
>>> ).
>>> Find still-open PRs that were created by a New Contributor 
>>> 
>>>  (an author who has no changes merged into our repository) or Contributor 
>>> 
>>>  (non-committer who has had some changes merged into our repository) or 
>>> Member 
>>> 
>>> Here are the uber-stale (last touched more than a month ago) open PRs by 
>>> outside contributors 
>>> .
>>>  We should ideally keep this at 0, but it’s 83 now!
>>> “Link to this search” to get a short-er, more permanent URL (it is NOT a 
>>> URL shortener, though!)
>>> Save named searches you frequently run (they just save to local cookie 
>>> state on that one browser)
>>> I’m sure there are exciting bugs, feedback/patches welcome!  If you see 
>>> problems, please reply to this email or file an issue here 
>>> .
>>> 
>>> Note that jirasearch  
>>> remains running, to search Solr, Tika and Infra issues.
>>> 
>>> Happy Searching,
>>> 
>>> Mike McCandless
>>> 
>>> http://blog.mikemccandless.com 
>> 
>> -- 
>> Anshum Gupta

Re: Announcing githubsearch!

[Alessandro Benedetti]

That's cool Mike! Well done!

On Wed, 21 Feb 2024, 22:02 Anshum Gupta,  wrote:

> This is great! Like always, thank you Mike!
>
> On Mon, Feb 19, 2024 at 8:40 AM Michael McCandless <
> luc...@mikemccandless.com> wrote:
>
>> Hi Team,
>>
>> ~1.5 years ago (August 2022) we migrated our Lucene issue tracking from
>> Jira to GitHub. Thank you Tomoko for all the hard work doing such a
>> complex, multi-phased, high-fidelity migration!
>>
>> I finally finished also migrating jirasearch to GitHub:
>> githubsearch.mikemccandless.com. It was tricky because GitHub issues/PRs
>> are fundamentally more complex than Jira's data model, and the GitHub REST
>> API is also quite rich / heavily normalized. All of the source code for
>> githubsearch lives here
>> .
>> The UI remains its barebones self ;)
>>
>> Githubsearch
>> 
>> is dog food for us: it showcases Lucene (currently 9.8.0), and many of its
>> fun features like infix autosuggest, block join queries (each comment is a
>> sub-document on the issue/PR), DrillSideways faceting, near-real-time
>> indexing/searching, synonyms (try “oome
>> ”),
>> expressions, non-relevance and blended-relevance sort, etc.  (This old
>> blog post
>> 
>>  goes
>> into detail.)  Plus, it’s meta-fun to use Lucene to search its own issues,
>> to help us be more productive in improving Lucene!  Nicely recursive.
>>
>> In addition to good ol’ searching by text, githubsearch
>>  has some new/fun features:
>>
>>- Drill down to just PRs or issues
>>- Filter by “review requested” for a given user: poor Adrien has 8
>>(open) now
>>
>> 
>>(sorry)! Or see your mentions (Robert is mentioned in 27 open
>>issues/PRs
>>
>> ).
>>Or PRs that you reviewed (Uwe has reviewed 9 still-open PRs
>>
>> ).
>>Or issues and PRs where a user has had any involvement at all (Dawid
>>has interacted on 197 issues/PRs
>>
>> 
>>).
>>- Find still-open PRs that were created by a New Contributor
>>
>> 
>>(an author who has no changes merged into our repository) or
>>Contributor
>>
>> 
>>(non-committer who has had some changes merged into our repository) or
>>Member
>>
>> 
>>- Here are the uber-stale (last touched more than a month ago) open
>>PRs by outside contributors
>>
>> .
>>We should ideally keep this at 0, but it’s 83 now!
>>- “Link to this search” to get a short-er, more permanent URL (it is
>>NOT a URL shortener, though!)
>>- Save named searches you frequently run (they just save to local
>>cookie state on that one browser)
>>
>> I’m sure there are exciting bugs, feedback/patches welcome!  If you see
>> problems, please reply to this email or file an issue here
>> .
>>
>> Note that jirasearch 
>> remains running, to search Solr, Tika and Infra issues.
>>
>> Happy Searching,
>>
>> Mike McCandless
>>
>> http://blog.mikemccandless.com
>>
>
>
> --
> Anshum Gupta
>

Re: Announcing githubsearch!

[Anshum Gupta]

This is great! Like always, thank you Mike!

On Mon, Feb 19, 2024 at 8:40 AM Michael McCandless <
luc...@mikemccandless.com> wrote:

> Hi Team,
>
> ~1.5 years ago (August 2022) we migrated our Lucene issue tracking from
> Jira to GitHub. Thank you Tomoko for all the hard work doing such a
> complex, multi-phased, high-fidelity migration!
>
> I finally finished also migrating jirasearch to GitHub:
> githubsearch.mikemccandless.com. It was tricky because GitHub issues/PRs
> are fundamentally more complex than Jira's data model, and the GitHub REST
> API is also quite rich / heavily normalized. All of the source code for
> githubsearch lives here
> .
> The UI remains its barebones self ;)
>
> Githubsearch
> 
> is dog food for us: it showcases Lucene (currently 9.8.0), and many of its
> fun features like infix autosuggest, block join queries (each comment is a
> sub-document on the issue/PR), DrillSideways faceting, near-real-time
> indexing/searching, synonyms (try “oome
> ”),
> expressions, non-relevance and blended-relevance sort, etc.  (This old
> blog post
> 
>  goes
> into detail.)  Plus, it’s meta-fun to use Lucene to search its own issues,
> to help us be more productive in improving Lucene!  Nicely recursive.
>
> In addition to good ol’ searching by text, githubsearch
>  has some new/fun features:
>
>- Drill down to just PRs or issues
>- Filter by “review requested” for a given user: poor Adrien has 8
>(open) now
>
> 
>(sorry)! Or see your mentions (Robert is mentioned in 27 open
>issues/PRs
>
> ).
>Or PRs that you reviewed (Uwe has reviewed 9 still-open PRs
>
> ).
>Or issues and PRs where a user has had any involvement at all (Dawid
>has interacted on 197 issues/PRs
>
> 
>).
>- Find still-open PRs that were created by a New Contributor
>
> 
>(an author who has no changes merged into our repository) or
>Contributor
>
> 
>(non-committer who has had some changes merged into our repository) or
>Member
>
> 
>- Here are the uber-stale (last touched more than a month ago) open
>PRs by outside contributors
>
> .
>We should ideally keep this at 0, but it’s 83 now!
>- “Link to this search” to get a short-er, more permanent URL (it is
>NOT a URL shortener, though!)
>- Save named searches you frequently run (they just save to local
>cookie state on that one browser)
>
> I’m sure there are exciting bugs, feedback/patches welcome!  If you see
> problems, please reply to this email or file an issue here
> .
>
> Note that jirasearch 
> remains running, to search Solr, Tika and Infra issues.
>
> Happy Searching,
>
> Mike McCandless
>
> http://blog.mikemccandless.com
>


-- 
Anshum Gupta

Re: Announcing githubsearch!

[Michael McCandless]

On Tue, Feb 20, 2024 at 10:06 AM Stefan Vodita 
wrote:

Thank you Mike, I really like all the facets!
>

Me too lol.  It was one of the big motivators for me to build this out.
GitHub's search didn't have all the facet drill-downs/up/sideways I
wanted.  Some of them are super useful like "which PRs have review
requested for me
"
or "where am I mentioned
".
Also, GitHub's filter choices do not seem to be dynamically generated for
this query -- so you can pick a filter value and it brings you to 0 hits,
violating the "no dead end" promise of Lucene's facets.

I was also disappointed with GitHub search's lack of hit highlighting, to
solve the "final inch" problem (show me specifically where, in this
massive massive list of comments on a PR/issue, my search terms appear),
and also not showing me the individual comment or code review comment
(multiple ones of those on a PR) where my search terms appear, lack of
linking directly to that comment, etc.  Githubsearch uses Lucene's block
joins to achieve this.

GitHub's search doesn't offer a blended relevance+recency sort, which I
think makes a great default.  It looks like it does support phrase search
(with double-quotes), curious how that works with ngrams.

I do like that the text query language includes all of the sort/filter
criteria -- the "is:open" and "sort:comments-desc".  Githubsearch doens't
support that through the text query language, just the facets UI / REST
query URL.

Anyway, I don't want to complain (too much) about GitHub's search efforts.
Search is clearly hard, and we all (Lucene experts) have a fairly
biased/opinionated take on it all, heh.  I've never met a search engine
that I'm fully happy with ;)

One thing that bothered me about GitHub's own search was that it would
> return
> different results if I wasn't signed in. Maybe it does early stopping for
> non-authenticated users? In any case, this won't be a problem with
> githubsearch.
>

Oh, that is very interesting -- I didn't know that.

Wow, I just tested -- indeed, you cannot even search the source code (for
Lucene's repo anyways) if you are not signed in.  That's weird.

For issues/PRs searching, the three queries I tried seem to produce the
same results signed in or out.  But it is scary/dangerous if this can
differ!!


> Have you considered indexing the Lucene source code too?
>

Oh my, I have not (until now lol).  That's a great idea.  Source code
tokenization would be such a fun problem ... I wonder if GitHub
open-sources how they tokenize the many different languages' source code.
GitHub's code search is in Rust (not using Lucene nor Rucene), a custom
search engine they recently built / switched to:
https://github.blog/2023-02-06-the-technology-behind-githubs-new-code-search,
away from Elasticsearch previously I think.  It looks like they use ngrams,
maybe instead of language-specific tokenization (?), to do the initial
matching/retrieval.  I would try normal lexical tokenization to see if
highlighting could work well.

I opened this luceneserver/GitHubSearch issue
 to think about this
... it'd sure be fun to build and use :)  Thank you for the suggestion
Stefan!

Mike McCandless

http://blog.mikemccandless.com

>

Re: Announcing githubsearch!

[Walter Underwood]

Oops, I followed a link which went to the main GitHub search. Nevermind.

I’m getting zero results for “wunder” now, no error. Looks like my username 
there is “wrunderwood”, that is working correctly as are quoted searches for my 
name.

I’l fool around some more, but so far it looks clean and fast. 

wunder
Walter Underwood
wun...@wunderwood.org
http://observer.wunderwood.org/  (my blog)

> On Feb 20, 2024, at 3:29 AM, Michael McCandless  
> wrote:
> 
> On Mon, Feb 19, 2024 at 1:00 PM Walter Underwood  > wrote:
> 
>> It appears to always search prefixes, so there is no way to search for 
>> “wunder” without getting “wundermap” and “wunderground”. Putting the term in 
>> quotes doesn’t turn that off.
> 
> Hmm that shouldn't be the case?  It does split on camel case though (thank 
> you WordDelimiterFilter!).  E.g. try searching on infix 
> 
>  and you should see it highlighted inside terms like AnalyzingInfixSuggester.
> 
> In fact when I search for wunder 
> 
>  I get a horrible exception, I think I know why (it happens for any query 
> that gets no hits!).  I opened this issue 
> .  I'll try to fix that 
> soon.
> 
> Walter, I'm not sure how you were able to even search on "wunder" -- did you 
> get actual results?  From githubsearch 
> ?
> 
> Mike McCandless
> 
> http://blog.mikemccandless.com 
> 

Re: Announcing githubsearch!

[Stefan Vodita]

Thank you Mike, I really like all the facets!

One thing that bothered me about GitHub's own search was that it would
return
different results if I wasn't signed in. Maybe it does early stopping for
non-authenticated users? In any case, this won't be a problem with
githubsearch.

Have you considered indexing the Lucene source code too?


Stefan

On Mon, 19 Feb 2024 at 16:40, Michael McCandless 
wrote:

> Hi Team,
>
> ~1.5 years ago (August 2022) we migrated our Lucene issue tracking from
> Jira to GitHub. Thank you Tomoko for all the hard work doing such a
> complex, multi-phased, high-fidelity migration!
>
> I finally finished also migrating jirasearch to GitHub:
> githubsearch.mikemccandless.com. It was tricky because GitHub issues/PRs
> are fundamentally more complex than Jira's data model, and the GitHub REST
> API is also quite rich / heavily normalized. All of the source code for
> githubsearch lives here
> .
> The UI remains its barebones self ;)
>
> Githubsearch
> 
> is dog food for us: it showcases Lucene (currently 9.8.0), and many of its
> fun features like infix autosuggest, block join queries (each comment is a
> sub-document on the issue/PR), DrillSideways faceting, near-real-time
> indexing/searching, synonyms (try “oome
> ”),
> expressions, non-relevance and blended-relevance sort, etc.  (This old
> blog post
> 
>  goes
> into detail.)  Plus, it’s meta-fun to use Lucene to search its own issues,
> to help us be more productive in improving Lucene!  Nicely recursive.
>
> In addition to good ol’ searching by text, githubsearch
>  has some new/fun features:
>
>- Drill down to just PRs or issues
>- Filter by “review requested” for a given user: poor Adrien has 8
>(open) now
>
> 
>(sorry)! Or see your mentions (Robert is mentioned in 27 open
>issues/PRs
>
> ).
>Or PRs that you reviewed (Uwe has reviewed 9 still-open PRs
>
> ).
>Or issues and PRs where a user has had any involvement at all (Dawid
>has interacted on 197 issues/PRs
>
> 
>).
>- Find still-open PRs that were created by a New Contributor
>
> 
>(an author who has no changes merged into our repository) or
>Contributor
>
> 
>(non-committer who has had some changes merged into our repository) or
>Member
>
> 
>- Here are the uber-stale (last touched more than a month ago) open
>PRs by outside contributors
>
> .
>We should ideally keep this at 0, but it’s 83 now!
>- “Link to this search” to get a short-er, more permanent URL (it is
>NOT a URL shortener, though!)
>- Save named searches you frequently run (they just save to local
>cookie state on that one browser)
>
> I’m sure there are exciting bugs, feedback/patches welcome!  If you see
> problems, please reply to this email or file an issue here
> .
>
> Note that jirasearch 
> remains running, to search Solr, Tika and Infra issues.
>
> Happy Searching,
>
> Mike McCandless
>
> http://blog.mikemccandless.com
>

Re: Announcing githubsearch!

[Chris Hegarty]

Awesome! I love it. Very useful.

-Chris.

> On 20 Feb 2024, at 11:40, Michael McCandless  
> wrote:
> 
> Thank you for all the warm feedback everyone, and all the exciting issues 
> already uncovered / ideas for improvements.  Now I have some more fun work to 
> do!
> 
> Mike McCandless
> 
> http://blog.mikemccandless.com
> 
> 
> On Mon, Feb 19, 2024 at 12:58 PM Julie Tibshirani  wrote:
> This is so cool! Thank you Mike for developing and hosting these services!
> 
> Julie
> 
> On Mon, Feb 19, 2024 at 9:40 AM Michael Wechner  
> wrote:
> thank you very much!
> 
> Am 19.02.24 um 17:39 schrieb Michael McCandless:
>> Hi Team,
>> 
>> ~1.5 years ago (August 2022) we migrated our Lucene issue tracking from Jira 
>> to GitHub. Thank you Tomoko for all the hard work doing such a complex, 
>> multi-phased, high-fidelity migration!
>> 
>> I finally finished also migrating jirasearch to GitHub: 
>> githubsearch.mikemccandless.com. It was tricky because GitHub issues/PRs are 
>> fundamentally more complex than Jira's data model, and the GitHub REST API 
>> is also quite rich / heavily normalized. All of the source code for 
>> githubsearch lives here. The UI remains its barebones self ;)
>> 
>> Githubsearch is dog food for us: it showcases Lucene (currently 9.8.0), and 
>> many of its fun features like infix autosuggest, block join queries (each 
>> comment is a sub-document on the issue/PR), DrillSideways faceting, 
>> near-real-time indexing/searching, synonyms (try “oome”), expressions, 
>> non-relevance and blended-relevance sort, etc.  (This old blog post goes 
>> into detail.)  Plus, it’s meta-fun to use Lucene to search its own issues, 
>> to help us be more productive in improving Lucene!  Nicely recursive.
>> 
>> In addition to good ol’ searching by text, githubsearch has some new/fun 
>> features:
>> • Drill down to just PRs or issues
>> • Filter by “review requested” for a given user: poor Adrien has 8 
>> (open) now (sorry)! Or see your mentions (Robert is mentioned in 27 open 
>> issues/PRs). Or PRs that you reviewed (Uwe has reviewed 9 still-open PRs). 
>> Or issues and PRs where a user has had any involvement at all (Dawid has 
>> interacted on 197 issues/PRs).
>> • Find still-open PRs that were created by a New Contributor (an author 
>> who has no changes merged into our repository) or Contributor (non-committer 
>> who has had some changes merged into our repository) or Member
>> • Here are the uber-stale (last touched more than a month ago) open PRs 
>> by outside contributors. We should ideally keep this at 0, but it’s 83 now!
>> • “Link to this search” to get a short-er, more permanent URL (it is NOT 
>> a URL shortener, though!)
>> • Save named searches you frequently run (they just save to local cookie 
>> state on that one browser)
>> I’m sure there are exciting bugs, feedback/patches welcome!  If you see 
>> problems, please reply to this email or file an issue here. 
>> 
>> Note that jirasearch remains running, to search Solr, Tika and Infra issues.
>> 
>> Happy Searching,
>> 
>> Mike McCandless
>> 
>> http://blog.mikemccandless.com
> 


-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Re: Announcing githubsearch!

[Michael McCandless]

Thank you for all the warm feedback everyone, and all the exciting issues
already uncovered / ideas for improvements.  Now I have some more fun work
to do!

Mike McCandless

http://blog.mikemccandless.com


On Mon, Feb 19, 2024 at 12:58 PM Julie Tibshirani 
wrote:

> This is so cool! Thank you Mike for developing and hosting these services!
>
> Julie
>
> On Mon, Feb 19, 2024 at 9:40 AM Michael Wechner 
> wrote:
>
>> thank you very much!
>>
>> Am 19.02.24 um 17:39 schrieb Michael McCandless:
>>
>> Hi Team,
>>
>> ~1.5 years ago (August 2022) we migrated our Lucene issue tracking from
>> Jira to GitHub. Thank you Tomoko for all the hard work doing such a
>> complex, multi-phased, high-fidelity migration!
>>
>> I finally finished also migrating jirasearch to GitHub:
>> githubsearch.mikemccandless.com. It was tricky because GitHub issues/PRs
>> are fundamentally more complex than Jira's data model, and the GitHub REST
>> API is also quite rich / heavily normalized. All of the source code for
>> githubsearch lives here
>> .
>> The UI remains its barebones self ;)
>>
>> Githubsearch
>> 
>> is dog food for us: it showcases Lucene (currently 9.8.0), and many of its
>> fun features like infix autosuggest, block join queries (each comment is a
>> sub-document on the issue/PR), DrillSideways faceting, near-real-time
>> indexing/searching, synonyms (try “oome
>> ”),
>> expressions, non-relevance and blended-relevance sort, etc.  (This old
>> blog post
>> 
>>  goes
>> into detail.)  Plus, it’s meta-fun to use Lucene to search its own issues,
>> to help us be more productive in improving Lucene!  Nicely recursive.
>>
>> In addition to good ol’ searching by text, githubsearch
>>  has some new/fun features:
>>
>>- Drill down to just PRs or issues
>>- Filter by “review requested” for a given user: poor Adrien has 8
>>(open) now
>>
>> 
>>(sorry)! Or see your mentions (Robert is mentioned in 27 open
>>issues/PRs
>>
>> ).
>>Or PRs that you reviewed (Uwe has reviewed 9 still-open PRs
>>
>> ).
>>Or issues and PRs where a user has had any involvement at all (Dawid
>>has interacted on 197 issues/PRs
>>
>> 
>>).
>>- Find still-open PRs that were created by a New Contributor
>>
>> 
>>(an author who has no changes merged into our repository) or
>>Contributor
>>
>> 
>>(non-committer who has had some changes merged into our repository) or
>>Member
>>
>> 
>>- Here are the uber-stale (last touched more than a month ago) open
>>PRs by outside contributors
>>
>> .
>>We should ideally keep this at 0, but it’s 83 now!
>>- “Link to this search” to get a short-er, more permanent URL (it is
>>NOT a URL shortener, though!)
>>- Save named searches you frequently run (they just save to local
>>cookie state on that one browser)
>>
>> I’m sure there are exciting bugs, feedback/patches welcome!  If you see
>> problems, please reply to this email or file an issue here
>> .
>>
>> Note that jirasearch 
>> remains running, to search Solr, Tika and Infra issues.
>>
>> Happy Searching,
>>
>> Mike McCandless
>>
>> http://blog.mikemccandless.com
>>
>>
>>

Re: Announcing githubsearch!

[Michael McCandless]

On Mon, Feb 19, 2024 at 1:00 PM Walter Underwood 
wrote:

It appears to always search prefixes, so there is no way to search for
> “wunder” without getting “wundermap” and “wunderground”. Putting the term
> in quotes doesn’t turn that off.
>

Hmm that shouldn't be the case?  It does split on camel case though (thank
you WordDelimiterFilter!).  E.g. try searching on infix

and
you should see it highlighted inside terms like AnalyzingInfixSuggester.

In fact when I search for wunder

I get a horrible exception, I think I know why (it happens for any query
that gets no hits!).  I opened this issue
.  I'll try to fix
that soon.

Walter, I'm not sure how you were able to even search on "wunder" -- did
you get actual results?  From githubsearch
?

Mike McCandless

http://blog.mikemccandless.com

Re: Announcing githubsearch!

[Michael McCandless]

On Tue, Feb 20, 2024 at 6:01 AM Michael Sokolov  wrote:

I love the gray all text UI. Don't change it! But I wonder if it's time for
> a favicon?
>

LOL favicon!  You do NOT want to have to confront my artistic skills!

Mike McCandless

http://blog.mikemccandless.com

>

Re: Announcing githubsearch!

[Michael Sokolov]

I love the gray all text UI. Don't change it! But I wonder if it's time for
a favicon?

On Tue, Feb 20, 2024, 4:40 AM Adrien Grand  wrote:

> Very cool, thank you Mike!
>
> On Mon, Feb 19, 2024 at 5:40 PM Michael McCandless <
> luc...@mikemccandless.com> wrote:
>
>> Hi Team,
>>
>> ~1.5 years ago (August 2022) we migrated our Lucene issue tracking from
>> Jira to GitHub. Thank you Tomoko for all the hard work doing such a
>> complex, multi-phased, high-fidelity migration!
>>
>> I finally finished also migrating jirasearch to GitHub:
>> githubsearch.mikemccandless.com. It was tricky because GitHub issues/PRs
>> are fundamentally more complex than Jira's data model, and the GitHub REST
>> API is also quite rich / heavily normalized. All of the source code for
>> githubsearch lives here
>> .
>> The UI remains its barebones self ;)
>>
>> Githubsearch
>> 
>> is dog food for us: it showcases Lucene (currently 9.8.0), and many of its
>> fun features like infix autosuggest, block join queries (each comment is a
>> sub-document on the issue/PR), DrillSideways faceting, near-real-time
>> indexing/searching, synonyms (try “oome
>> ”),
>> expressions, non-relevance and blended-relevance sort, etc.  (This old
>> blog post
>> 
>>  goes
>> into detail.)  Plus, it’s meta-fun to use Lucene to search its own issues,
>> to help us be more productive in improving Lucene!  Nicely recursive.
>>
>> In addition to good ol’ searching by text, githubsearch
>>  has some new/fun features:
>>
>>- Drill down to just PRs or issues
>>- Filter by “review requested” for a given user: poor Adrien has 8
>>(open) now
>>
>> 
>>(sorry)! Or see your mentions (Robert is mentioned in 27 open
>>issues/PRs
>>
>> ).
>>Or PRs that you reviewed (Uwe has reviewed 9 still-open PRs
>>
>> ).
>>Or issues and PRs where a user has had any involvement at all (Dawid
>>has interacted on 197 issues/PRs
>>
>> 
>>).
>>- Find still-open PRs that were created by a New Contributor
>>
>> 
>>(an author who has no changes merged into our repository) or
>>Contributor
>>
>> 
>>(non-committer who has had some changes merged into our repository) or
>>Member
>>
>> 
>>- Here are the uber-stale (last touched more than a month ago) open
>>PRs by outside contributors
>>
>> .
>>We should ideally keep this at 0, but it’s 83 now!
>>- “Link to this search” to get a short-er, more permanent URL (it is
>>NOT a URL shortener, though!)
>>- Save named searches you frequently run (they just save to local
>>cookie state on that one browser)
>>
>> I’m sure there are exciting bugs, feedback/patches welcome!  If you see
>> problems, please reply to this email or file an issue here
>> .
>>
>> Note that jirasearch 
>> remains running, to search Solr, Tika and Infra issues.
>>
>> Happy Searching,
>>
>> Mike McCandless
>>
>> http://blog.mikemccandless.com
>>
>
>
> --
> Adrien
>

Re: Announcing githubsearch!

[Adrien Grand]

Very cool, thank you Mike!

On Mon, Feb 19, 2024 at 5:40 PM Michael McCandless <
luc...@mikemccandless.com> wrote:

> Hi Team,
>
> ~1.5 years ago (August 2022) we migrated our Lucene issue tracking from
> Jira to GitHub. Thank you Tomoko for all the hard work doing such a
> complex, multi-phased, high-fidelity migration!
>
> I finally finished also migrating jirasearch to GitHub:
> githubsearch.mikemccandless.com. It was tricky because GitHub issues/PRs
> are fundamentally more complex than Jira's data model, and the GitHub REST
> API is also quite rich / heavily normalized. All of the source code for
> githubsearch lives here
> .
> The UI remains its barebones self ;)
>
> Githubsearch
> 
> is dog food for us: it showcases Lucene (currently 9.8.0), and many of its
> fun features like infix autosuggest, block join queries (each comment is a
> sub-document on the issue/PR), DrillSideways faceting, near-real-time
> indexing/searching, synonyms (try “oome
> ”),
> expressions, non-relevance and blended-relevance sort, etc.  (This old
> blog post
> 
>  goes
> into detail.)  Plus, it’s meta-fun to use Lucene to search its own issues,
> to help us be more productive in improving Lucene!  Nicely recursive.
>
> In addition to good ol’ searching by text, githubsearch
>  has some new/fun features:
>
>- Drill down to just PRs or issues
>- Filter by “review requested” for a given user: poor Adrien has 8
>(open) now
>
> 
>(sorry)! Or see your mentions (Robert is mentioned in 27 open
>issues/PRs
>
> ).
>Or PRs that you reviewed (Uwe has reviewed 9 still-open PRs
>
> ).
>Or issues and PRs where a user has had any involvement at all (Dawid
>has interacted on 197 issues/PRs
>
> 
>).
>- Find still-open PRs that were created by a New Contributor
>
> 
>(an author who has no changes merged into our repository) or
>Contributor
>
> 
>(non-committer who has had some changes merged into our repository) or
>Member
>
> 
>- Here are the uber-stale (last touched more than a month ago) open
>PRs by outside contributors
>
> .
>We should ideally keep this at 0, but it’s 83 now!
>- “Link to this search” to get a short-er, more permanent URL (it is
>NOT a URL shortener, though!)
>- Save named searches you frequently run (they just save to local
>cookie state on that one browser)
>
> I’m sure there are exciting bugs, feedback/patches welcome!  If you see
> problems, please reply to this email or file an issue here
> .
>
> Note that jirasearch 
> remains running, to search Solr, Tika and Infra issues.
>
> Happy Searching,
>
> Mike McCandless
>
> http://blog.mikemccandless.com
>


-- 
Adrien

Re: Announcing githubsearch!

[Alexandre Rafalovitch]

Next step towards full meta would be by writing a Lucene Introduction
book,  using code examples from this project and the dataset this project
uses.

Regards,
Alex

On Mon, Feb 19, 2024, 11:40 a.m. Michael McCandless <
luc...@mikemccandless.com> wrote:

> Hi Team,
>
> ~1.5 years ago (August 2022) we migrated our Lucene issue tracking from
> Jira to GitHub. Thank you Tomoko for all the hard work doing such a
> complex, multi-phased, high-fidelity migration!
>
> I finally finished also migrating jirasearch to GitHub:
> githubsearch.mikemccandless.com. It was tricky because GitHub issues/PRs
> are fundamentally more complex than Jira's data model, and the GitHub REST
> API is also quite rich / heavily normalized. All of the source code for
> githubsearch lives here
> .
> The UI remains its barebones self ;)
>
> Githubsearch
> 
> is dog food for us: it showcases Lucene (currently 9.8.0), and many of its
> fun features like infix autosuggest, block join queries (each comment is a
> sub-document on the issue/PR), DrillSideways faceting, near-real-time
> indexing/searching, synonyms (try “oome
> ”),
> expressions, non-relevance and blended-relevance sort, etc.  (This old
> blog post
> 
>  goes
> into detail.)  Plus, it’s meta-fun to use Lucene to search its own issues,
> to help us be more productive in improving Lucene!  Nicely recursive.
>
> In addition to good ol’ searching by text, githubsearch
>  has some new/fun features:
>
>- Drill down to just PRs or issues
>- Filter by “review requested” for a given user: poor Adrien has 8
>(open) now
>
> 
>(sorry)! Or see your mentions (Robert is mentioned in 27 open
>issues/PRs
>
> ).
>Or PRs that you reviewed (Uwe has reviewed 9 still-open PRs
>
> ).
>Or issues and PRs where a user has had any involvement at all (Dawid
>has interacted on 197 issues/PRs
>
> 
>).
>- Find still-open PRs that were created by a New Contributor
>
> 
>(an author who has no changes merged into our repository) or
>Contributor
>
> 
>(non-committer who has had some changes merged into our repository) or
>Member
>
> 
>- Here are the uber-stale (last touched more than a month ago) open
>PRs by outside contributors
>
> .
>We should ideally keep this at 0, but it’s 83 now!
>- “Link to this search” to get a short-er, more permanent URL (it is
>NOT a URL shortener, though!)
>- Save named searches you frequently run (they just save to local
>cookie state on that one browser)
>
> I’m sure there are exciting bugs, feedback/patches welcome!  If you see
> problems, please reply to this email or file an issue here
> .
>
> Note that jirasearch 
> remains running, to search Solr, Tika and Infra issues.
>
> Happy Searching,
>
> Mike McCandless
>
> http://blog.mikemccandless.com
>

Re: Announcing githubsearch!

[David Smiley]

Cool Mike!

On Mon, Feb 19, 2024 at 11:41 AM Michael McCandless
 wrote:
>
> Hi Team,
>
> ~1.5 years ago (August 2022) we migrated our Lucene issue tracking from Jira 
> to GitHub. Thank you Tomoko for all the hard work doing such a complex, 
> multi-phased, high-fidelity migration!
>
> I finally finished also migrating jirasearch to GitHub: 
> githubsearch.mikemccandless.com. It was tricky because GitHub issues/PRs are 
> fundamentally more complex than Jira's data model, and the GitHub REST API is 
> also quite rich / heavily normalized. All of the source code for githubsearch 
> lives here. The UI remains its barebones self ;)
>
> Githubsearch is dog food for us: it showcases Lucene (currently 9.8.0), and 
> many of its fun features like infix autosuggest, block join queries (each 
> comment is a sub-document on the issue/PR), DrillSideways faceting, 
> near-real-time indexing/searching, synonyms (try “oome”), expressions, 
> non-relevance and blended-relevance sort, etc.  (This old blog post goes into 
> detail.)  Plus, it’s meta-fun to use Lucene to search its own issues, to help 
> us be more productive in improving Lucene!  Nicely recursive.
>
> In addition to good ol’ searching by text, githubsearch has some new/fun 
> features:
>
> Drill down to just PRs or issues
> Filter by “review requested” for a given user: poor Adrien has 8 (open) now 
> (sorry)! Or see your mentions (Robert is mentioned in 27 open issues/PRs). Or 
> PRs that you reviewed (Uwe has reviewed 9 still-open PRs). Or issues and PRs 
> where a user has had any involvement at all (Dawid has interacted on 197 
> issues/PRs).
> Find still-open PRs that were created by a New Contributor (an author who has 
> no changes merged into our repository) or Contributor (non-committer who has 
> had some changes merged into our repository) or Member
> Here are the uber-stale (last touched more than a month ago) open PRs by 
> outside contributors. We should ideally keep this at 0, but it’s 83 now!
> “Link to this search” to get a short-er, more permanent URL (it is NOT a URL 
> shortener, though!)
> Save named searches you frequently run (they just save to local cookie state 
> on that one browser)
>
> I’m sure there are exciting bugs, feedback/patches welcome!  If you see 
> problems, please reply to this email or file an issue here.
>
> Note that jirasearch remains running, to search Solr, Tika and Infra issues.
>
> Happy Searching,
>
> Mike McCandless
>
> http://blog.mikemccandless.com

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Re: Announcing githubsearch!

[Walter Underwood]

It appears to always search prefixes, so there is no way to search for “wunder” 
without getting “wundermap” and “wunderground”. Putting the term in quotes 
doesn’t turn that off.

wunder
Walter Underwood
wun...@wunderwood.org
http://observer.wunderwood.org/  (my blog)

> On Feb 19, 2024, at 8:39 AM, Michael McCandless  
> wrote:
> 
> Hi Team,
> 
> ~1.5 years ago (August 2022) we migrated our Lucene issue tracking from Jira 
> to GitHub. Thank you Tomoko for all the hard work doing such a complex, 
> multi-phased, high-fidelity migration!
> 
> I finally finished also migrating jirasearch to GitHub: 
> githubsearch.mikemccandless.com . 
> It was tricky because GitHub issues/PRs are fundamentally more complex than 
> Jira's data model, and the GitHub REST API is also quite rich / heavily 
> normalized. All of the source code for githubsearch lives here 
> .
>  The UI remains its barebones self ;)
> 
> Githubsearch 
> 
>  is dog food for us: it showcases Lucene (currently 9.8.0), and many of its 
> fun features like infix autosuggest, block join queries (each comment is a 
> sub-document on the issue/PR), DrillSideways faceting, near-real-time 
> indexing/searching, synonyms (try “oome 
> ”),
>  expressions, non-relevance and blended-relevance sort, etc.  (This old blog 
> post 
> 
>  goes into detail.)  Plus, it’s meta-fun to use Lucene to search its own 
> issues, to help us be more productive in improving Lucene!  Nicely recursive.
> 
> In addition to good ol’ searching by text, githubsearch 
>  has some new/fun features:
> Drill down to just PRs or issues
> Filter by “review requested” for a given user: poor Adrien has 8 (open) now 
> 
>  (sorry)! Or see your mentions (Robert is mentioned in 27 open issues/PRs 
> ).
>  Or PRs that you reviewed (Uwe has reviewed 9 still-open PRs 
> ).
>  Or issues and PRs where a user has had any involvement at all (Dawid has 
> interacted on 197 issues/PRs 
> ).
> Find still-open PRs that were created by a New Contributor 
> 
>  (an author who has no changes merged into our repository) or Contributor 
> 
>  (non-committer who has had some changes merged into our repository) or 
> Member 
> 
> Here are the uber-stale (last touched more than a month ago) open PRs by 
> outside contributors 
> .
>  We should ideally keep this at 0, but it’s 83 now!
> “Link to this search” to get a short-er, more permanent URL (it is NOT a URL 
> shortener, though!)
> Save named searches you frequently run (they just save to local cookie state 
> on that one browser)
> I’m sure there are exciting bugs, feedback/patches welcome!  If you see 
> problems, please reply to this email or file an issue here 
> .
> 
> Note that jirasearch  
> remains running, to search Solr, Tika and Infra issues.
> 
> Happy Searching,
> 
> Mike McCandless
> 
> http://blog.mikemccandless.com 

Re: Announcing githubsearch!

[Julie Tibshirani]

This is so cool! Thank you Mike for developing and hosting these services!

Julie

On Mon, Feb 19, 2024 at 9:40 AM Michael Wechner 
wrote:

> thank you very much!
>
> Am 19.02.24 um 17:39 schrieb Michael McCandless:
>
> Hi Team,
>
> ~1.5 years ago (August 2022) we migrated our Lucene issue tracking from
> Jira to GitHub. Thank you Tomoko for all the hard work doing such a
> complex, multi-phased, high-fidelity migration!
>
> I finally finished also migrating jirasearch to GitHub:
> githubsearch.mikemccandless.com. It was tricky because GitHub issues/PRs
> are fundamentally more complex than Jira's data model, and the GitHub REST
> API is also quite rich / heavily normalized. All of the source code for
> githubsearch lives here
> .
> The UI remains its barebones self ;)
>
> Githubsearch
> 
> is dog food for us: it showcases Lucene (currently 9.8.0), and many of its
> fun features like infix autosuggest, block join queries (each comment is a
> sub-document on the issue/PR), DrillSideways faceting, near-real-time
> indexing/searching, synonyms (try “oome
> ”),
> expressions, non-relevance and blended-relevance sort, etc.  (This old
> blog post
> 
>  goes
> into detail.)  Plus, it’s meta-fun to use Lucene to search its own issues,
> to help us be more productive in improving Lucene!  Nicely recursive.
>
> In addition to good ol’ searching by text, githubsearch
>  has some new/fun features:
>
>- Drill down to just PRs or issues
>- Filter by “review requested” for a given user: poor Adrien has 8
>(open) now
>
> 
>(sorry)! Or see your mentions (Robert is mentioned in 27 open
>issues/PRs
>
> ).
>Or PRs that you reviewed (Uwe has reviewed 9 still-open PRs
>
> ).
>Or issues and PRs where a user has had any involvement at all (Dawid
>has interacted on 197 issues/PRs
>
> 
>).
>- Find still-open PRs that were created by a New Contributor
>
> 
>(an author who has no changes merged into our repository) or
>Contributor
>
> 
>(non-committer who has had some changes merged into our repository) or
>Member
>
> 
>- Here are the uber-stale (last touched more than a month ago) open
>PRs by outside contributors
>
> .
>We should ideally keep this at 0, but it’s 83 now!
>- “Link to this search” to get a short-er, more permanent URL (it is
>NOT a URL shortener, though!)
>- Save named searches you frequently run (they just save to local
>cookie state on that one browser)
>
> I’m sure there are exciting bugs, feedback/patches welcome!  If you see
> problems, please reply to this email or file an issue here
> .
>
> Note that jirasearch 
> remains running, to search Solr, Tika and Infra issues.
>
> Happy Searching,
>
> Mike McCandless
>
> http://blog.mikemccandless.com
>
>
>

Re: Announcing githubsearch!

[Michael Wechner]

thank you very much!

Am 19.02.24 um 17:39 schrieb Michael McCandless:

Hi Team,

~1.5 years ago (August 2022) we migrated our Lucene issue tracking 
from Jira to GitHub. Thank you Tomoko for all the hard work doing such 
a complex, multi-phased, high-fidelity migration!


I finally finished also migrating jirasearch to GitHub: 
githubsearch.mikemccandless.com 
. It was tricky because 
GitHub issues/PRs are fundamentally more complex than Jira's data 
model, and the GitHub REST API is also quite rich / heavily 
normalized. All of the source code for githubsearch lives here 
. 
The UI remains its barebones self ;)


Githubsearch 
 
is dog food for us: it showcases Lucene (currently 9.8.0), and many of 
its fun features like infix autosuggest, block join queries (each 
comment is a sub-document on the issue/PR), DrillSideways faceting, 
near-real-time indexing/searching, synonyms (try “oome 
”), 
expressions, non-relevance and blended-relevance sort, etc.  (This old 
blog post 
 goes 
into detail.)  Plus, it’s meta-fun to use Lucene to search its own 
issues, to help us be more productive in improving Lucene! Nicely 
recursive.


In addition to good ol’ searching by text, githubsearch 
 has some new/fun features:


  * Drill down to just PRs or issues
  * Filter by “review requested” for a given user: poor Adrien has 8
(open) now


(sorry)! Or see your mentions (Robert is mentioned in 27 open
issues/PRs

).
Or PRs that you reviewed (Uwe has reviewed 9 still-open PRs

).
Or issues and PRs where a user has had any involvement at all
(Dawid has interacted on 197 issues/PRs

).
  * Find still-open PRs that were created by a New Contributor


(an author who has no changes merged into our repository) or
Contributor


(non-committer who has had some changes merged into our
repository) or Member


  * Here are the uber-stale (last touched more than a month ago) open
PRs by outside contributors

.
We should ideally keep this at 0, but it’s 83 now!
  * “Link to this search” to get a short-er, more permanent URL (it is
NOT a URL shortener, though!)
  * Save named searches you frequently run (they just save to local
cookie state on that one browser)

I’m sure there are exciting bugs, feedback/patches welcome!  If you 
see problems, please reply to this email or file an issue here 
.


Note that jirasearch  
remains running, to search Solr, Tika and Infra issues.


Happy Searching,

Mike McCandless

http://blog.mikemccandless.com

Announcing githubsearch!

[Michael McCandless]

Hi Team,

~1.5 years ago (August 2022) we migrated our Lucene issue tracking from
Jira to GitHub. Thank you Tomoko for all the hard work doing such a
complex, multi-phased, high-fidelity migration!

I finally finished also migrating jirasearch to GitHub:
githubsearch.mikemccandless.com. It was tricky because GitHub issues/PRs
are fundamentally more complex than Jira's data model, and the GitHub REST
API is also quite rich / heavily normalized. All of the source code for
githubsearch lives here
.
The UI remains its barebones self ;)

Githubsearch

is dog food for us: it showcases Lucene (currently 9.8.0), and many of its
fun features like infix autosuggest, block join queries (each comment is a
sub-document on the issue/PR), DrillSideways faceting, near-real-time
indexing/searching, synonyms (try “oome
”),
expressions, non-relevance and blended-relevance sort, etc.  (This old blog
post

goes
into detail.)  Plus, it’s meta-fun to use Lucene to search its own issues,
to help us be more productive in improving Lucene!  Nicely recursive.

In addition to good ol’ searching by text, githubsearch
 has some new/fun features:

   - Drill down to just PRs or issues
   - Filter by “review requested” for a given user: poor Adrien has 8
   (open) now
   

   (sorry)! Or see your mentions (Robert is mentioned in 27 open issues/PRs
   
).
   Or PRs that you reviewed (Uwe has reviewed 9 still-open PRs
   
).
   Or issues and PRs where a user has had any involvement at all (Dawid has
   interacted on 197 issues/PRs
   

   ).
   - Find still-open PRs that were created by a New Contributor
   

   (an author who has no changes merged into our repository) or Contributor
   

   (non-committer who has had some changes merged into our repository) or
   Member
   

   - Here are the uber-stale (last touched more than a month ago) open PRs
   by outside contributors
   
.
   We should ideally keep this at 0, but it’s 83 now!
   - “Link to this search” to get a short-er, more permanent URL (it is NOT
   a URL shortener, though!)
   - Save named searches you frequently run (they just save to local cookie
   state on that one browser)

I’m sure there are exciting bugs, feedback/patches welcome!  If you see
problems, please reply to this email or file an issue here
.

Note that jirasearch 
remains running, to search Solr, Tika and Infra issues.

Happy Searching,

Mike McCandless

http://blog.mikemccandless.com