-
-
Notifications
You must be signed in to change notification settings - Fork 46.8k
Unresponsive PRs and issues #1155
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
Comments
My sense is that we should implement #1134. It is better if it is automated using GitHub's tool rather than doing it manually. |
One of the reason why #1134 should be accepted. |
@cclauss I agree. Doing so manually is tedious and it is also not my intention considering the number of open PRs. But we have to do this ASAP so we can focus only on PRs which are important and close the ones which are unnecessary and unresponsive. |
@AnupKumarPanwar @dynamitechetan @r0hit-gupta I've sent the request to install stale. |
@harshildarji I have approved the request. Please go forward. |
@r0hit-gupta Hey, Thanks for approving this. It's installed but since I do not have permission to configure it, you'll have to do it as an owner. |
I do not have the rights to turn this on but it should be turned on. |
@cclauss I think so. I also do not have rights for that! |
I think using GitHub actions to check stale issues and PRs can be done now, since GitHub Actions is open for public. |
https://github.com/marketplace/stale is all we need. It is free from GitHub. Someone with Admin privileges just needs to turn in on. |
I was suggesting we use this |
To
@cclauss@AnupKumarPanwar @poyeaHey all,
At this moment, we have over 150 PRs. Some of these are requested changes by the reviewers, but there is no response from the PR makers after that. Some PRs are months old which now may cause conflicts with current implementations if merged.
Therefore, I plan to close such PRs which have no response from people who made it or is months old which might break an existing implementation.
But before doing so, I would like to know what other members think about this.
Thank you.
Best regards,
Harshil Darji
The text was updated successfully, but these errors were encountered: