-
Notifications
You must be signed in to change notification settings - Fork 353
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
Only-label shoud act as a filter #1046
Comments
Hello, @ov7a ! Thanks for creating the issue! We'll do some investigation and see what seems to be the problem :) |
@dsame Thank you for the reply. Could you please provide more details on why it's not possible? The statefulness is a great feature! However, I think it’s only a partial solution to the problem. Consider a case when a repository has 2000+ open issues, but only 100 of them have some label. Full scan is 20x times slower. It also wastes a lot resources. |
Hello @ov7a, to know the labels of the issue, it has to be fetched first. This is the limitation of GitHub REST API used by stale action. The migration to GraphQL is not planned at the moment. The fetching bunch of issue is just one GitHub API call, so it does not affect reaching limit of API rate greatly. |
I don't think this is true. API has |
I made a PR: #1084 |
Description/Justification:
I'm running a stale action with "only-labels" setting. I expect it to act as a filter, so only issues/prs labeled with particular labels are considered during the run.
However, the current behavior is to do a full-scan. It drains the operation limit very fast.
The text was updated successfully, but these errors were encountered: