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
[ci] switch to a supported no-response bot #5060
Comments
Just re-opening to discuss one more thing. I just saw this comment posted by the new action: #5039 (comment)
|
@jameslamb It is okay for me, but bot account is better. |
According to the https://github.com/lee-dohm/no-response#inputs,
Docs: https://docs.github.com/en/actions/security-guides/automatic-token-authentication We just need to replace
and closing comment will be posted by github-actions [bot] account.
Example: |
oh excellent find @StrikerRUS , thanks!! Ok great, I'll put up a PR with that change. Then people won't respond to those comments by tagging @guolinke 😂 |
Closed by #5136. |
This issue has been automatically locked since there has not been any recent activity since it was closed. To start a new related discussion, open a new issue at https://github.com/microsoft/LightGBM/issues including a reference to this. |
Description
This project uses
probot/no-response
to automatically close issues where the original poster has stops interacting with the issue.I noticed today that that project is no longer supported.
As of July 2021, the README at https://github.com/probot/no-response reads as follows:
This project should switch to https://github.com/lee-dohm/no-response, to limit the risk of this useful automation failing due to incompatibilities with future GitHub Actions changes.
Additional Comments
Noticed this while considering a contribution to dask/community#60 and reading the discussion there.
The text was updated successfully, but these errors were encountered: