One may think of iterating all the issues with GitHub REST/GraphQL API and filter them when label. It MAY be possible for GraphQL but NEVER for REST API since it have to iterate almost all the (open) issues and we'd quickly exceed any rate limit (as we have over 2000 repos and many many issues ...). It's also slow because REST API returns a full object for the issue every time.
Best, tison. tison <wander4...@gmail.com> 于2024年10月25日周五 02:03写道： > > To list help wanted issues on our repository, try: > > https://github.com/search?q=org:apache+label:%22help+wanted%22&type=issues > https://github.com/search?q=org:apache+label:%22help+wanted%22&type=pullrequests > https://github.com/search?q=org:apache+label:%22help+wanted%22&type=discussions > > There are some GitHub APIs for this search interface: > > https://docs.github.com/en/rest/search/search?apiVersion=2022-11-28 > https://docs.github.com/en/graphql/reference/queries#search > > But I don't check it closely and the three URLs above should be easier > to start with. > > Best, > tison. > > sebb <seb...@gmail.com> 于2024年10月25日周五 00:02写道： > > > > On Thu, 24 Oct 2024 at 16:36, Xuanwo <xua...@apache.org> wrote: > > > > > > +1 to shut it down. > > > > > > We can rebuild it using GitHub APIs as needed, eliminating the need for > > > heavy infrastructure like Elasticsearch. > > > > Are you offering to help build it? > > > > > On Thu, Oct 24, 2024, at 23:23, Christopher wrote: > > > > An alternative would be to automatically link to open issues in > > > > GitHub.com/Apache with specific tags, like "help wanted" or "good first > > > > issue". This is similar to what hacktoberfest does to help participants > > > > discover new issues. Merely having a listing of issues on GitHub would > > > > be > > > > much easier to support than maintaining a site that manages its own > > > > authentication, issue submission, and database. > > > > > > > > On Thu, Oct 24, 2024, 11:17 Rich Bowen <rbo...@rcbowen.com> wrote: > > > > > > > >> > > > >> > > > >> > On Oct 24, 2024, at 10:04 AM, sebb <seb...@gmail.com> wrote: > > > >> > > > > >> > The helpwanted.a.o service uses ElasticSearch (ES). > > > >> > However, the current version is rather old. > > > >> > This was causing issues with Puppet server deployment. > > > >> > > > > >> <…> > > > >> > ** So is there any point in keeping the system running, or should it > > > >> > be shut down? ** > > > >> > > > >> I was actually under the impression that we *had* shut it down. So, > > > >> yes, I > > > >> would be +1 to decomm it entirely. It was a great idea that projects > > > >> never > > > >> really utilized, and as such was never very useful in practice. :( > > > >> > > > >> — > > > >> Rich Bowen > > > >> rbo...@rcbowen.com > > > >> > > > >> > > > >> > > > >> > > > >> > > > > > > -- > > > Xuanwo > > > > > > https://xuanwo.io/ > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > > > For additional commands, e-mail: dev-h...@community.apache.org > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > > For additional commands, e-mail: dev-h...@community.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
