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

Option to ignore either PR's or Issues #837

Open
Safihre opened this issue Oct 3, 2022 · 12 comments
Open

Option to ignore either PR's or Issues #837

Safihre opened this issue Oct 3, 2022 · 12 comments
Labels
enhancement New feature or request feature request New feature or request to improve the current logic need eyes Feature request needs additional triaging by leads

Comments

@Safihre
Copy link

Safihre commented Oct 3, 2022

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)?

@Safihre
Copy link
Author

Safihre commented Oct 4, 2022

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.
I want to prevent it from even looking at issues, so it can look at more PR's.

@github-actions
Copy link
Contributor

github-actions bot commented Nov 5, 2022

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

@github-actions github-actions bot added the Stale label Nov 5, 2022
@Safihre
Copy link
Author

Safihre commented Nov 5, 2022

No not stale. Just nobody cared to respond.

@github-actions github-actions bot removed the Stale label Nov 6, 2022
@github-actions
Copy link
Contributor

github-actions bot commented Dec 7, 2022

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

@github-actions github-actions bot added the Stale label Dec 7, 2022
@steveluscher
Copy link

Duplicate of #792.

@Safihre
Copy link
Author

Safihre commented Dec 7, 2022

Is it? That issue is not very clearly described as being the same problem. It might be, but then should be more clearly described.

@steveluscher
Copy link

Oh, I thought they were.

This issue:

However, due to the huge amount of PR's it never gets near to the newer PR's because it runs out of operations.

That issue:

The stale bot uses up all my API actions on iterating over existing stale commits and checking them for comments, and it never gets to apply the stale label to everything that needs it.

Aren't both of your issues about operation overhead in the processor preventing your repositories from being exhaustively processed before exhausting your operations budget?

@Safihre
Copy link
Author

Safihre commented Dec 7, 2022

Yes, but for different underlying reasons. So a solution for one will most likely not resolve the other.

@github-actions github-actions bot removed the Stale label Dec 8, 2022
@codebydant
Copy link

I am looking for the same configuration. I just want to scan PRs instead issues.

@codebydant
Copy link

This seems to be related to #688

@kurtqq
Copy link

kurtqq commented Jul 16, 2023

this is much needed one!
any chance it will be added in future version?

@dsame dsame added feature request New feature or request to improve the current logic need eyes Feature request needs additional triaging by leads labels Aug 8, 2023
@testworksau
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request feature request New feature or request to improve the current logic need eyes Feature request needs additional triaging by leads
Projects
None yet
Development

No branches or pull requests

6 participants