Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature: Ability to send a list of repos instead of just one #26

Closed
zkoppert opened this issue Jun 16, 2023 · 5 comments · Fixed by #107
Closed

Feature: Ability to send a list of repos instead of just one #26

zkoppert opened this issue Jun 16, 2023 · 5 comments · Fixed by #107
Labels
enhancement New feature or request

Comments

@zkoppert
Copy link
Member

It would be nice to feed it a list of repositories instead of just one repo. The use case for this would be: As a maintainer, I want to check my response rate and close rate for issues and PRs in open source projects that I maintain.

@zkoppert zkoppert added the enhancement New feature or request label Jun 16, 2023
@zkoppert
Copy link
Member Author

@Okabe-Junya
Copy link
Contributor

Hi!!

I added this example to the README in #93, but do you mean to provide this within the CI workflow? I might be able to work on this issue. (It might take me some time, though...)

@zkoppert
Copy link
Member Author

zkoppert commented Aug 7, 2023

Yes, Here I am talking about being able to do this in the search query like this. GitHub search has this nice OR capability so I thought it would be good to add an example of using this to the readme:
SEARCH_QUERY: repo:github-linguist/linguist OR repo:tree-sitter/tree-sitter is:issue

@Okabe-Junya
Copy link
Contributor

Hi!!!

I apologize for the considerable delay in my response, as I didn't notice the notification for this issue.

The link you commented on seems quite valuable, but it looks like a syntax for a code search query. We might want to consult documents like this because our aim is to search for issues. To "OR" multiple repos, perhaps you can simply list the repo names in the query.

Here's a simple example.

Search query: repo:Okabe-Junya/sandbox repo:Okabe-Junya/dotfiles is:issue created:2022-07-01..2023-07-31 -reason:"not planned" resulted in Okabe-Junya/sandbox#218 (most of them are in Japanese, though).

I can create a PR to fix #93. This method appears to be more efficient.

Thank you.

@Okabe-Junya
Copy link
Contributor

As a maintainer, I want to check my response rate and close rate for issues and PRs in open source projects that I maintain.

For your purpose, the "involve" operator might be very useful.

Search by a user that's involved in an issue or pull request

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants