Thank you Michael! Adrien
Le ven. 25 juil. 2025, 19:36, Michael Froh <msf...@gmail.com> a écrit : > I was able to close the project, which GitHub says will cancel all > associated workflows, so hopefully that's it. > > I'll keep an eye out to see if it keeps triggering. > > On Fri, Jul 25, 2025 at 10:33 AM Michael Froh <msf...@gmail.com> wrote: > >> Ahh... sorry about that. That was a (in my opinion misplaced) attempt by >> a former AWS OpenSearch manager to improve visibility into Lucene changes >> that could potentially impact OpenSearch (which essentially means every >> Lucene change). In practice, we ended up just doing regular >> reviews/discussions of the Lucene changelog, which was far more practical >> than a GitHub project. >> >> I'll see if I have permission to kill that project and the auto-tagging >> rule. If I don't, I'll reach out to the manager who set it up. >> >> On Fri, Jul 25, 2025 at 10:22 AM Dawid Weiss <dawid.we...@gmail.com> >> wrote: >> >>> >>> I've been wondering about it myself. I think it's github being github - >>> public cross-references show up in issue audit/history. >>> >>> Dawid >>> >>> On Fri, Jul 25, 2025 at 4:03 PM Adrien Grand <jpou...@gmail.com> wrote: >>> >>>> Hello all, >>>> >>>> All issues / PRs get added to the "OpenSearch Lucene & Core >>>> Performance Tracking" GitHub project, which adds notifications on every >>>> issue/PR, see attached screenshot. This isn't a huge deal, but it requires >>>> more scrolling between the issue/PR description and the first actual >>>> comment, which adds up when browsing many issues / PRs. >>>> >>>> While the project may be useful to the OpenSearch team, I don't think >>>> that having these notifications on Lucene issues/PRs brings any value? Does >>>> anyone know if it's possible to skip them? >>>> >>>> -- >>>> Adrien >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org >>>> For additional commands, e-mail: dev-h...@lucene.apache.org >>> >>>
