-
Notifications
You must be signed in to change notification settings - Fork 369
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
Option to ignore either PR's or Issues #837
Comments
I know, but that's not what this is about. It will not label them, but it will still process them at the cost of API actions. |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days |
No not stale. Just nobody cared to respond. |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days |
Duplicate of #792. |
Is it? That issue is not very clearly described as being the same problem. It might be, but then should be more clearly described. |
Oh, I thought they were. This issue:
That issue:
Aren't both of your issues about operation overhead in the processor preventing your repositories from being exhaustively processed before exhausting your operations budget? |
Yes, but for different underlying reasons. So a solution for one will most likely not resolve the other. |
I am looking for the same configuration. I just want to scan PRs instead issues. |
This seems to be related to #688 |
this is much needed one! |
I'd be keen to see this functionality too, in some repos I want issues to remain open forever, and PRs to be closed after they become stale. |
The cpython project runs the stale action to only mark PR's as stale.
However, due to the huge amount of PR's it never gets near to the newer PR's because it runs out of operations.
See: https://github.com/python/cpython/blob/9151bbefea3fb932eb6aa6ddb22d64b83f8149c7/.github/workflows/stale.yml
The action could process many more PR's if the issues would not be checked at all, since no action is defined for them anyway.
Could there be a way to force the action to skip issues (or PR's, for someone that just wants to check issues)?
The text was updated successfully, but these errors were encountered: